Skip to content
Snippets Groups Projects

Support CI `paths`, `project`, and `ref` subkeys in `rules:exists`

Merged Leaminn Ma requested to merge ci-rules-exists-add-paths-project-ref into master
2 files
+ 10
8
Compare changes
  • Side-by-side
  • Inline
Files
2
+ 2
2
@@ -4222,7 +4222,7 @@ job:
FLAG:
On self-managed GitLab, by default this feature is not available.
To make it available, an administrator can [enable the feature flag](../administration/feature_flags.md) named `ci_support_rules_exists_paths_and_project`.
To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md) named `ci_support_rules_exists_paths_and_project`.
On GitLab.com and GitLab Dedicated, this feature is not available.
`rules:exists:paths` is the same as using [`rules:exists`](#rulesexists) without
@@ -4261,7 +4261,7 @@ In this example, both jobs have the same behavior.
FLAG:
On self-managed GitLab, by default this feature is not available.
To make it available, an administrator can [enable the feature flag](../administration/feature_flags.md) named `ci_support_rules_exists_paths_and_project`.
To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md) named `ci_support_rules_exists_paths_and_project`.
On GitLab.com and GitLab Dedicated, this feature is not available.
Use `rules:exists:project` to specify the location in which to search for the files
Loading