On Friday, March 16, 2018 at 5:39:09 PM UTC-4, Abhishek Gautam wrote: > > > *@martinda * > While my research I came across something called EnvironmentContributor in > Jenkins. Do you think that we can use this to pass required variables to > the build processes? >
Hi Abhishek, I have never used the EnvironmentContributor, but it would be one of the possibilities. Injecting environment variables is convenient as all sub-commands would inherit them (no explicit argument passing required), it is an implementation detail which can be decided later. I suggest that you try the existing functionality (see Jesse's reply), and this will help you to write your own project proposal. The existing plugins that I think Jesse is referring to are https://jenkins.io/doc/book/pipeline/multibranch/ and https://go.cloudbees.com/docs/cloudbees-documentation/cje-user-guide/index.html#bitbucket. The example projects that seem to go along with these plugins are https://github.com/cloudbeers/multibranch-demo and https://github.com/cloudbeers/multibranch-demo-lib Like Oleg said, the project idea description is not a specification, it does not have to be followed to the letter. BR, Martin -- 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/9e0fec3a-9cfa-454e-9ce9-aa18e7d94bb2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
