> On 12. Aug 2018, at 13:40, Dário Nascimento <[email protected]> wrote: > > I want to execute a plugin using Jenkinsfile pipeline and I want that plugin > to have the context (branch & job) without user interference. This plugin > generates a token identifying the job so we can authenticate with other > services. > If I allow users to set the branch as env var, then the token content is > compromised and my plugin is insecure. This is critical to developing a > secure self-service CI/CD. How can I do it? >
https://jenkins.io/blog/2018/05/15/incremental-deployment/ might help you. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA5FBA4D-822D-4F40-8800-1B52A355BD54%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
