|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Not to be confused with credentials support in a Step or a compatible SCM or SimpleBuildStep implementation: this is about not just picking a credentialsId to pass on to another Step, but using the secrets held in the Credentials directly in some other way, such as in sh.
Current workaround is to define a credentials parameter for the flow, giving it a default value. This means that Build Now is replaced with Build with Parameters, even though you do not need to actually do anything except confirm, which is unfortunate. (Scheduled builds should still run fine.)