### Problem to solve I have some CI jobs which run the same steps on different files and try to DRY my CI by using `extends`. However, GitLab does not currently evaluate variables in `rules:changes`, which makes this difficult. I can work around it by replacing `extends` with the explicit properties, but it makes my CI file unnecessarily verbose. When setting an environment variable as a path and using that variable in rules:changes, the variable is ignored. #### Example 1. Create a env variable named `HELM_DIR` and set it to `helm` in the UI. 2. Create a project that contains `helm/test.txt` 3. Add the below `gitlab-ci.yml` script to the project: ```yml test0: script: - echo "This is test0 and will complete" - echo $CI_COMMIT_BRANCH - echo $CI_PROJECT_DIR test1: script: - echo $CI_COMMIT_BRANCH - echo $CI_PROJECT_DIR - echo $HELM_DIR - echo "This is working" - ls rules: - if: $CI_COMMIT_BRANCH changes: - $HELM_DIR/**/* when: on_success ``` 4. Make a change to the `helm/test.txt` file or any file in that folder. *The below works when explicitly setting the file path*: ```yml test0: script: - echo "This is test0 and will complete" - echo $CI_COMMIT_BRANCH - echo $CI_PROJECT_DIR test1: script: - echo $CI_COMMIT_BRANCH - echo $CI_PROJECT_DIR - echo "This is working" - ls rules: - if: $CI_COMMIT_BRANCH changes: - helm/**/* when: on_success ``` ### Intended users <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ --> ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> Benefit would be cleaner-looking CI that is easier to maintain. ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> Support variable use in the `rules:changes` clause Note that `$` is a valid character in a path, so we need to enforce a rule that if `$SOMETHING` variable exists then we will replace it, otherwise we should leave `$SOMETHING` unchanged. ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?--> No impact ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements If this feature requires changing permissions, this document https://docs.gitlab.com/ee/user/permissions.html must be updated accordingly. --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further help: https://about.gitlab.com/handbook/engineering/quality/test-engineering/ --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> Support variable use in the `rules:changes` clause ### What is the type of buyer? <!-- Which leads to: in which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> Any tier where `rules:changes` is available (i.e. free/core and above) ### Links / references <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *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.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->