Handle missing gitlab-ci.yml files using compliance pipelines
Problem to solve
Currently, a project without a GitLab CI configuration file (.gitlab-ci.yml
) are not supported by compliance pipelines as the compliance pipeline configuration is merged with the project's CI configuration file. When that file doesn't exist, it cannot be merged.
groupcompliance has attempted a couple of general solutions to fix this problem which added features to the CI YAML schema. Both were rejected at code review but the general problem stil exists and we need to propose a way forward.
Attempted solutions
Add project/file options to exists rules
MR: !75250 (closed)
Add optional: keyword to include statement
MR: !81421 (closed)
Proposal
Full context in parent epic. This issue is intended to allow an issue to go through the workflow label states for the use case detailed in the parent epic.
Intended users
Feature Usage Metrics
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.