New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow secure variables (environment) on environments, stages and jobs level #194
Comments
Also on environment level please! |
This is probably a duplicate of #107. |
arikagoyal/mdaliejaz; any chance this will make it into any upcoming release? |
I would really appreciate this feature in the upcoming release; it's vital for keeping sensitive information secured in the build and the lack of it leads to some convoluted/unnecessary workarounds that makes the pipelines hard to maintain. |
+1 to this. At the moment we have pipeline explosion as we need to create new pipelines every time we need to run the same job but with different secure variables. |
Picking this up! |
…stage-and-job-level Allow secure variables (environment) on stages, jobs and environments level (#194).
…stage-and-job-level Fixed the failing test #194.
#1161 - implements support for environment, stage & job level secure env. vars. |
(enhancement)
Is there a good reason for only allowing secure variables (environment) on the pipeline level? If not it would be great also to have this option on pipeline group, stage and job level.
edit: pipeline group level does not support env. vars
The text was updated successfully, but these errors were encountered: