Yes! I had to echo all the environment variables into the properties file
using the format:
echo "PARAM1=${PARAM1}" >> myprops.properties
(make sure your first echo has ">" instead of ">>", so the file gets
initialized)
The child build then had all those values!!!
--
View this message in con
Hmmm, the latest version of the Parameterized Trigger plugin (2.25) has this
(see the ***):
--
This plugin lets you trigger new builds when your build has completed, with
various ways of specifying parameters for the new build. You can add
multiple configurations: each has a list of projects t
On Thu, Jul 31, 2014 at 1:51 PM, Greg Hansen wrote:
> I haven't had the time to learn both Groovy and the Jenkins context. Was
> looking for a plugin or a recipe to copy.
>
Mostly the same here - I think you can do about anything in groovy but
you don't get the fill-in-the-form options But
AM
To: jenkinsci-users
Subject: Re: Share environment variables between jobs
On Thu, Jul 31, 2014 at 1:46 PM, GregHansen wrote:
> A partial solution would be allow build steps to set the values of
> job-level parameters, which could then be passed by the Parameterized
> Trigger plugin to the
On Thu, Jul 31, 2014 at 1:46 PM, GregHansen wrote:
> A partial solution would be allow build steps to set the values of job-level
> parameters, which could then be passed by the Parameterized Trigger plugin
> to the child job. In my case, I would like to do this from within a shell
> build step. S
A partial solution would be allow build steps to set the values of job-level
parameters, which could then be passed by the Parameterized Trigger plugin
to the child job. In my case, I would like to do this from within a shell
build step. Simple parameter-passing
--
View this message in cont
On Thu, Jul 31, 2014 at 1:22 PM, GregHansen wrote:
>
> It's things like this that make Jenkins awkward to use for complete
> workflows, where a continuous environment between jobs makes sense.
You could probably do it with the build-flow plugin, but given its
status and the fact that it requires
Archiving the file only works if the parent job completes before triggering
the child job. At least in my case, I'm using the Parameterized Trigger
plugin as a build step, taking advantage of the built-in joining capability
that it gives, and then want to perform some action depending on the succes
