Problem/Motivation
The test-only issue #3386566: Add support for 'test only' changes to gitlab CI commit introduced dump of all variables in the GitlabCI again. This was Fixed by #3387916: Each GitLab job exposes user email in the past. See the relevant code:
'🩹 Test-only changes':
...
script:
...
- export
We should remove the export, as the purpose was only for debugging.
Steps to reproduce
See the test-only job output: https://git.drupalcode.org/issue/drupal-2820586/-/jobs/132773
Proposed resolution
Remove the export.
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
Issue fork drupal-3391114
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
poker10 commentedComment #4
poker10 commentedComment #5
smustgrave commentedLGTM
Comment #7
catchCommitted/pushed to 11.x and cherry-picked to 10.1.x, thanks!
Comment #9
jonathan1055 commentedFor info, in the contrib gitlab template we changed this so that the variables can be exported, but are not done by default. Also even when exported, the personal gitlab variables are removed. See #3388207: Allow showing debug information and the associated MR gitlab_templates/-/merge_requests/45
The specific change to solve this, and remove all the GITLAB_USER variables was
env | sort | sed -E '/^(GITLAB_USER).*/d'Comment #10
poker10 commentedThanks. If this will be beneficial for core, let's create a child issue here #3387107: [meta] GitLab CI feature parity with DrupalCI, so that something similar can be added to core as well (this fix was only about the test-only job, but I think that we would then want to allow exports for all jobs, not only this one).