An error occurred while fetching this tab.
Support CI `paths`, `project`, and `ref` subkeys in `rules:exists`
- Apr 10, 2024
-
-
Leaminn Ma authored
Added spec examples to test when the rules:exists subkeys 'project' and 'ref' are invalid and they have unmasked variables.
-
- Apr 09, 2024
-
-
Leaminn Ma authored
-
Leaminn Ma authored
-
- Apr 08, 2024
-
-
Leaminn Ma authored
Accessed the instance variables directly in find_project and find_sha instead of passing them along.
-
Leaminn Ma authored
Adds the ability to specify the context in which `rules:exists` searches for the given file paths. The subkeys `paths`, `project`, and `ref` can be specified. If `project` is specified but not `ref`, the default `ref` is the project's HEAD. If `project` is not specified, the defaults are as follows: For `job:rules:exists`, the default context is the project/ref in which the pipeline is running. For `include:rules:exists`, the default context is the project/ref of the file in which the `include` is declared. These changes are made behind a Feature flag: `ci_support_rules_exists_paths_and_project`
-