You have two jobs, Job1 calling Job2. The parameter $JOB_NAME is local to each job, so in Job2 the value of $JOB_NAME is Job2. Add an additional param in Job1 ($JOB_1_NAME=$JOB_NAME) and use it in Job2. FYI, any value that's empty means that the parameter value is undefined. Check spellings too.
On Thursday, October 23, 2014 3:16:46 PM UTC-7, Adam Mercer wrote: > > Hi > > Hi > > I'm trying to tie a couple of jobs together using the Parametrized > Trigger Plugin and am running into problems with the second job > finding the libraries built by the first job. > > When the first job completes successfully I trigger a build of the > second job, I'm forcing it to use the same node so that it can find > the libraries. In the first job I install the libraries to a location > on the build slave dependent upon the JOB_NAME and BUILD_NUMBER > variables. I use the Parametrized Trigger Plugin to pass these onto > the second job. However it look like that value of JOB_NAME that is > getting passed on is incorrect and as such the library can't be found > by the second job and the build fails. > > In order to start debugging this I printed out the value of JOB_NAME > from the first job and the value that was passed to the second job, > they differed. In the first job JOB_NAME is set to > LALSuite/LAL/label=sl6 whereas is the second job it is seeing > LALSuite/LAL, i.e. the label=sl6 is being dropped. > > Any ideas why this label information is not being passed along? > > Cheers > > Adam > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
