-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
Our workflow uses branches for feature development, qa and releases to production. This different environments have credentials attached to them. For code merges go through a review stage and only authorized folks can perform merges to certain branches. We have just started using jenkins pipeline with the withCredentials step. It would be awesome if we could limit access to credentials when specific branches are being built. Ie it should not be possible to get a credential for production when a feature/* branch is being built.
- relates to
-
JENKINS-27398 Pipeline-as-Code CredentialsProvider for a job
- Open