That is worth investigating, thanks! On Apr 2, 2014, at 4:28 AM, [email protected] wrote:
> You can use the EnvInject plugin to set a job-wide environment > > From: Kevin Fleming (BLOOMBERG/ 731 LEXIN) [mailto:[email protected]] > Sent: 01 April 2014 22:22 > To: [email protected] > Subject: Re:Parameterized build parameter help > > What do you mean by 'you have a job trigger'? If you mean that you have a > child job triggered by the completion of the first one, then any environment > variables you set in the build steps in the first job will not carry over to > the child job. Any changes you make in the environment inside a build step > will only exist for the lifetime of that build step; in the next build step, > or any post-build steps, or child jobs, they will not be visible. There is no > job-wide environment. > > ----- Original Message ----- > From: [email protected] > To: [email protected] > At: Apr 1 2014 17:09:43 > I hope I can explain this clearly enough the first time around. > > I have a parameterized build. > > Under "This build is parameterized", I have added three choices: > > TEST_ARGS, which accepts a string > TEST_GROUP_A, which is a "choice" > TEST_GROUP_B, which is also a "choice" > > I have these broken out for clarity. > > In the BUILD section the first thing I do is: > > export TEST_ARGS="${TEST_ARGS} ${TEST_GROUP_A,} ${TEST_GROUP_B}" > > This, in theory, puts the entirety of "TEST_ARGS" into the shell as an > environment variable. > > Next, I have a job trigger; however, that job is not getting the full string. > Only the original TEST_ARGS string that the user typed into the first > parameter. I have "Current Build Parameters" selected. I have also tried to > add "Predefined Parameters" and define TEST_ARGS=$TEST_ARGS, since it says I > can use "build parameters and/or environment variables." > > Either way, I can only get the original TEST_ARGS string to be passed all the > way through. > > Any suggestions? > > I have these split out because parameters 2 and 3 are optional and to make > things more clear for my users. However, I have muddied the waters for > Jenkins, or myself. > > -silver > > -- > 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 [email protected]. > 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 [email protected]. > 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 [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
