Permit access to protected CI variables on merge train builds
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
When configuring my pipeline I would like to configure it such that all my "master" build and release happens in the "merge train" pipeline, such that in the event of it failing, nothing is merged. When doing so I would like to take advantage of the "Protected" variables to execute release activities.
Intended users
This would typically be used by development leads, devops engineers or release managers to ensure continued prodictivity by "keeping master green" while executing release activities.
User experience goal
The user should be able to configure their project's pipelines to have protected variables accessible to merge train jobs.
Proposal
The user would find the new configuration option in the project settings which enable this level of access. When this is configured the additional variables would be available to merge train pipelines.
Permissions and Security
Configuring this would require high level (admin) access to the project. Accidental misconfiguration of this could be equivalent to having protected variables unprotected.
Documentation
This would need documentation in, ideally, both the variables and merge trains documentation.