Perhaps the label=sl6 is getting parsed as another parameter?? Try \'ing it:  
label\=sl6

-----Original Message-----
From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Adam Mercer
Sent: Wednesday, November 05, 2014 5:40 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Passing environment variables using the parameterized trigger 
plugin

On Wed, Nov 5, 2014 at 4:30 PM, Dunnigan, Terrence J 
<terrence.j.dunni...@boeing.com> wrote:

> Are you using a recent version of Jenkins and the parameterized plugin?

The current LTS release and the latest parameterized plugin, at least Jenkins 
tells me that no updates are available for my plugins.

> I suspect the problem is that you are defining $PREFIX locally on the 
> machine, and then trying to reference it via a Jenkins job configuration. 
> When I’ve encountered that situation I’ve worked around it by writing the 
> value to a .properties file and then passing that file to the downstream job 
> (using the ‘Parameters from a properties file’) option.

That sounds like what I'm going to need to do.

> As for the other environment variables, passing $JOB_NAME and $BUILD_NUMBER 
> work just fine for me.

BUILD_NUMBER works without an issue, JOB_NAME is only partially passed. The 
value is Job1 is "LALSuite/LAL/label=sl6" but only "LALSuite/LAL" is passed to 
Job2, the label=sl6 part is dropped.

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.

-- 
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.

Reply via email to