Skip to content

Perform build environment printing in a different block

Balasankar 'Balu' C requested to merge fix-omnibus-env-target-branch into master

What does this MR do and why?

As seen from https://gitlab.com/gitlab-org/gitlab/-/jobs/4242121728#L61, the echo used for user message might be flowing to the env file and cause issues with TRIGGER_BRANCH being jibberish. Let's separate the file generation and printing into two different blocks.

Also, make the env file available as an artifact for debugging.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports