Re: EnvInject global vs. per job behavior

2012-04-26 Thread shanz 
I've recently used the EnvInject plugin on several concurrent jobs.
I created a file with the variables in it :-
eg: 
MY_FIRST_VAR=whatever
MY_NEXT_VAR=somethingElse

Then I tick the box on any job which needs access to either variable and 
point to the file.

Re: EnvInject global vs. per job behavior

2012-04-26 Thread Grégory Boissinot 
On Tue, Apr 24, 2012 at 3:10 AM, AnthonyJ anthony.jeff...@cox.net wrote:

 If one job is enabled for EnvInject, should it affect all jobs
 globally?

no


 I see the message below for jobs which do not have it turned on..

 [EnvInject] - Preparing an environment for the build.

the current build of the current job


 One of my colleagues even showed me a case where setting a built in
 jenkins env variable used by other jobs gets corrupted/set in the
 other jobs.

Could you try to isolate the problem?
Then raise a bug report and attach your configuration files.



 Thanks,
 Anthony

EnvInject global vs. per job behavior

2012-04-23 Thread AnthonyJ 
If one job is enabled for EnvInject, should it affect all jobs
globally?

I see the message below for jobs which do not have it turned on..

[EnvInject] - Preparing an environment for the build.

One of my colleagues even showed me a case where setting a built in
jenkins env variable used by other jobs gets corrupted/set in the
other jobs.

Thanks,
Anthony