Debug in expand_composer.
Closes #3441816
Merge request reports
Activity
- Resolved by Fran Garcia-Linares
132 132 ``` 133 133 - !reference [ .create-environment-variables ] 134 134 ``` 135 136 ## Running pipelines via the GitLab UI 137 138 You can run pipelines from the GitLab UI navigating to: `Build` > `Pipelines` > `Run pipeline`. When you do this, all the variables inherited from the templates will show in the form and you can override any value, which will take priority over any pre-defined value or value set in the `.gitlab-ci.yml` file. 139 140 If you have opted in to any of the variants (next or previous minor or major) and want to run the pipelines from the GitLab UI, make sure that you remove the `_TARGET_CORE` variable from the form as this would invalidate the value set for each variant. changed this line in version 13 of the diff
No longer applicable and removed anyway. But I cannot close this thread.
Edited by Jonathan Smith
added 1 commit
- a0ea6d5e - Add .non-global-vars to default: so every job gets them
added 1 commit
- e4ba6272 - Override _TARGET_CORE and _TARGET_PHP via create-environment-variables
added 1 commit
- 7e576b0e - Define OVERRIDE variables in phpunit, phpstan and nightwatch
544 544 COMPOSER_PATCHES_FILE: 545 545 value: "" 546 546 description: "DEPRECATED: Use _COMPOSER_PATCHES_FILE instead (with a leading underscore)." 547 548 # testing to see if non-global variables are shown in the Run Pipelines form 549 .non-global-vars: &non-global-vars 550 variables: 551 IS_THIS_IN_THE_FORM: 552 value: "$_TARGET_CORE" - Comment on lines +548 to +552
Just noting here, that we are not using this method for the
OVERRIDE_
core and php values. But we possibly could move into this group a whole bunch of the variables for which we say "do not change these". That is not taking away any functionality, because if a maintainer reads the variables.yml file they can still add the variable on the form. But they will not be shown by default. changed this line in version 13 of the diff
Yes it is similar. But
.test-variables
is only used in phpunit and nighwatch, so we'd need to create a new name for all these, and use it at the very top level. I have just pushed a first attempt at this.Edited by Jonathan Smith
added 4 commits
-
7e576b0e...472ef130 - 3 commits from branch
project:main
- 5682d990 - Merge branch gitlab_templates:main into 3441816-check-version-of-core
-
7e576b0e...472ef130 - 3 commits from branch
added 1 commit
- 90960875 - Use reference as the definition is an another file