I did something similar for the saucelabs plugin
https://github.com/jenkinsci/sauce-ondemand-plugin/blob/master/src/main/java/com/saucelabs/jenkins/pipeline/SauceStep.java#L66
This produces sauce {} block (due to takesImplicitBlockArgument) which
makes a new context with new environment variables.
On Wednesday, April 27, 2016 at 5:19:07 PM UTC-7, Owen B. Mehegan wrote:
>
> I help maintain the Jenkins GitLab plugin, and a recent major refactor (by
> someone else) broke our rudimentary Pipeline job type support. We have
> clawed our way back to partial support now, where I can get the plugin to
> trigger a Pipeline job, but we're stuck on the fact that none of the
> necessary parameters for the build are set. Looking at our code, I think
> the problem is that we use setUpEnvironment() for that, which I understand
> doesn't make sense in Pipeline. I'm not sure where we should go from here.
> There is a more complete explanation of my findings, with links to the
> relevant code, here:
> https://github.com/jenkinsci/gitlab-plugin/issues/271#issuecomment-215270683
>
--
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/c273b125-e3e2-4025-81ad-3903728b545b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
