Ok, the use of global varaibles/parameters is pretty simple, merely set them in
the
manage jenkins ->configure system->Global Properties-> environment variables
and set a series of name/value pairs. In the jenkins job I reference them in
the ANT properties box as name=${Global_property_1}. In
I do not think tha the build pipeline uses build flows. Also, when I look at
teh build flow plugin, they state that it is a POC plugin and it seems tha the
developers are moving on and suggest the use of the workflow plugin. It seems
that there has to be some way to set global variables and us
I'm using the build flow plugin, which I believe is used by the build
pipeline.
Basically my groovy script that orchestrates the build flow passes in some
variables to the build calls in build flow. I don't have to define the
parameters on the build job that I am calling with the parameters.
On
Mike:
Thanks for the reply. I'm not sure I follow the response. When you mention
Build Flows are you talking about build pipeline creating using the build
pipeline plugin? Also, who are you setting the values that you pass in?
Thanks, Eric
On Wednesday, June 4, 2014 3:34 PM, Mike Chmielewsk
For Build Flows, I have passed in arbitrary variables not defined on a job
in the flow, and they are picked up correctly.
On Wed, Jun 4, 2014 at 12:42 PM, Eric Wood wrote:
> I have several jenkins jobs that I want to use global variables. The only
> way I have seen to do this is to parameteriz
I have several jenkins jobs that I want to use global variables. The only way
I have seen to do this is to parameterize my build and to set a global
parameter string using the plugin documented here:
https://wiki.jenkins-ci.org/display/JENKINS/Global+Variable+String+Parameter+Plugin
The issue