Hello, I have similar case and I get the theory but cannot make it work. I have job A which is git poll job and as post build action it triggers build B using parametrized trigger plugin with "predefined parameter": gitCommit=$GIT_COMMIT But I don't know how to read this parameter in job B. "env" command in shell script doesn't show it. I tried various combinations with e.g. gitCommit=someConstant and with "Pass through git commit" but just can't make it working.
Would someone share the details of how to pass "id" (at best git commit id) down the pipeline? thanks Lukasz On Tuesday, February 21, 2012 12:55:32 AM UTC+1, Geoff Bullen wrote: > > The join plugin doesn't work with the build pipeline plugin. However you > can achieve pretty much the same thing by wrapping up multiple jobs a build > steps using the parametrised triggers plugin > > In terms of passing artefacts down a pipeline of jobs, what I tend to do > is pass a unique identifier along the pipeline that is used to publish the > built artefact early on and to retrieve built artefacts later on. You can > use the copy artefact plugin to pass built artefacts around as well >
