Re: Passing environment variables using the parameterized trigger plugin

2014-11-13 Thread Adam Mercer
On Fri, Nov 7, 2014 at 7:17 AM, Daniel Beck m...@beckweb.net wrote: Is the downstream build triggered for every matrix axis that finishes building, or only once, when all axes finished? Sorry for the delay I've been busy with getting a release out of the door. The downstream build is

Re: Passing environment variables using the parameterized trigger plugin

2014-11-13 Thread Daniel Beck
On 13.11.2014, at 22:21, Adam Mercer r...@gravity.phys.uwm.edu wrote: The downstream build is triggered when all axes are finished. So it behaves correctly. The label part is only part of the sub-builds (where the project name has the suffix with the active axis values), not the overall

Re: Passing environment variables using the parameterized trigger plugin

2014-11-13 Thread Adam Mercer
On Thu, Nov 13, 2014 at 4:17 PM, Daniel Beck m...@beckweb.net wrote: So it behaves correctly. The label part is only part of the sub-builds (where the project name has the suffix with the active axis values), not the overall build (which does not), and if the trigger is run once for the

Re: Passing environment variables using the parameterized trigger plugin

2014-11-07 Thread Daniel Beck
Is the downstream build triggered for every matrix axis that finishes building, or only once, when all axes finished? On 07.11.2014, at 05:46, Adam Mercer r...@gravity.phys.uwm.edu wrote: On Thu, Nov 6, 2014 at 4:15 PM, Ginga, Dick dick.gi...@perkinelmer.com wrote: Change the jobname to

RE: Passing environment variables using the parameterized trigger plugin

2014-11-06 Thread Ginga, Dick
@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

Re: Passing environment variables using the parameterized trigger plugin

2014-11-06 Thread Adam Mercer
On Thu, Nov 6, 2014 at 7:15 AM, Ginga, Dick dick.gi...@perkinelmer.com wrote: Perhaps the label=sl6 is getting parsed as another parameter?? Try \'ing it: label\=sl6 Interesting idea, that kind of makes sense. The problem is that there's nothing for me to escape, as label=sl6 is part of

RE: Passing environment variables using the parameterized trigger plugin

2014-11-06 Thread Ginga, Dick
variables using the parameterized trigger plugin On Thu, Nov 6, 2014 at 7:15 AM, Ginga, Dick dick.gi...@perkinelmer.com wrote: Perhaps the label=sl6 is getting parsed as another parameter?? Try \'ing it: label\=sl6 Interesting idea, that kind of makes sense. The problem is that there's nothing

Re: Passing environment variables using the parameterized trigger plugin

2014-11-06 Thread Adam Mercer
On Thu, Nov 6, 2014 at 4:15 PM, Ginga, Dick dick.gi...@perkinelmer.com wrote: Change the jobname to labl:sl6? Or labl-sl6? I can't, that's what Jenkins assigns. The job itself is called LAL and the matrix plugin adds /label=sl6, /label=wheezy, etc... depending on which operating system I'm

Passing environment variables using the parameterized trigger plugin

2014-11-05 Thread Adam Mercer
Hi According to the documentation for the Parameterized Trigger plugin, specifically for 'Predefined parameters: KEY=value pairs, one per line (Java properties file format). Backslashes are used for escaping, so use \\ for a single backslash. Current build parameters and/or environment

RE: Passing environment variables using the parameterized trigger plugin

2014-11-05 Thread Dunnigan, Terrence J
, 2014 4:14 PM To: jenkinsci-users@googlegroups.com Subject: Passing environment variables using the parameterized trigger plugin Hi According to the documentation for the Parameterized Trigger plugin, specifically for 'Predefined parameters: KEY=value pairs, one per line (Java properties

Re: Passing environment variables using the parameterized trigger plugin

2014-11-05 Thread Adam Mercer
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.