Hi
I am calling parameterized build using below , where RELEASE_VERSION = 1.0
, DEV_BUILD = 1 and SVN_REVISON=227
PROD_VERSION=$RELEASE_VERSION.$DEV_BUILD_$SVN_REVISION
the parameter used in called build as PROD_VERSION=1.0.$DEV_BUILD_227
am I need to do something different to get PROD_VERS
On Thu, Nov 13, 2014 at 4:17 PM, Daniel Beck 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 overall build,
>
On 13.11.2014, at 22:21, Adam Mercer 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
build (which does not), and i
On Fri, Nov 7, 2014 at 7:17 AM, Daniel Beck 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 triggered when all axes
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 wrote:
> On Thu, Nov 6, 2014 at 4:15 PM, Ginga, Dick
> wrote:
>> Change the jobname to labl:sl6? Or labl-sl6?
>
> I can't, that's what Je
variables using the parameterized trigger
plugin
On Thu, Nov 6, 2014 at 4:15 PM, Ginga, Dick 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... depen
On Thu, Nov 6, 2014 at 4:15 PM, Ginga, Dick 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 trying to build on. I build the
variables using the parameterized trigger
plugin
On Thu, Nov 6, 2014 at 7:15 AM, Ginga, Dick 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
On Thu, Nov 6, 2014 at 7:15 AM, Ginga, Dick 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 JOB_NAME
itself.
Cheers
Adam
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
wrote:
> Are you using a recent version of Jenkins and the parameterized plugin?
The current LTS release and the latest parameterized plugin,
On Wed, Nov 5, 2014 at 4:30 PM, Dunnigan, Terrence J
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 t
, 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
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 va
13 matches
Mail list logo
