Bug 496917

Comment 1 David Williams 2016-06-28 13:07:33 EDT

I have "renamed" the Hudson test jobs on "shared" and "CentOS". 

Just adding 1 to the number in the name of the test, for MNIY. 

For "performance" machine, I have done half of them, for N and I. 

Tip for Performance tests: 

I don't know if you have noticed, but they run in a certain order, each "lower" test triggering the "higher" test. Here is the order or  I builds, for example: 

ep47I-perf-lin64-baseline
ep47I-perf-lin64
ep47ILR-perf-lin64-baseline
ep47ILR-perf-lin64

In other words, there are "two names" associated with each job: the job name itself, and the job that it is to trigger after it is done. 

So, if you go in reverse order, that "job-to-trigger" is updated automatically, so you only have one name to change. If you do not go in reverse order, you get all kinds of warnings that "the trigger job does not exist" and end up having to change it in two places and perhaps making two passes. 

To be concrete, in above example, I renamed this one first: 

ep4*ILR-perf-lin64

Since it does not trigger any further jobs, it is safe just to rename the job. Once you do, the trigger job in ep4*ILR-perf-lin64-baseline is updated automatically, So then when you change name of ep4*ILR-perf-lin64-baseline it updates trigger job in ep4*I-perf-lin64 ... etc. 

Did you try to rename jobs? Not sure if you have the right permissions to, but if you wanted to try the "M" and "Y" performance jobs (and you can do soon) then give it a try, otherwise I'll finish those up before end of day.

Comment 2 Sravan Kumar Lakkimsetti 2016-06-29 06:04:06 EDT

(In reply to David Williams from comment #1)
> I have "renamed" the Hudson test jobs on "shared" and "CentOS". 
> 
> Just adding 1 to the number in the name of the test, for MNIY. 
> 
> For "performance" machine, I have done half of them, for N and I. 
> 
> Tip for Performance tests: 
> 
> I don't know if you have noticed, but they run in a certain order, each
> "lower" test triggering the "higher" test. Here is the order or  I builds,
> for example: 
> 
> ep47I-perf-lin64-baseline
> ep47I-perf-lin64
> ep47ILR-perf-lin64-baseline
> ep47ILR-perf-lin64
> 
> In other words, there are "two names" associated with each job: the job name
> itself, and the job that it is to trigger after it is done. 
> 
> So, if you go in reverse order, that "job-to-trigger" is updated
> automatically, so you only have one name to change. If you do not go in
> reverse order, you get all kinds of warnings that "the trigger job does not
> exist" and end up having to change it in two places and perhaps making two
> passes. 
> 
> To be concrete, in above example, I renamed this one first: 
> 
> ep4*ILR-perf-lin64
> 
> Since it does not trigger any further jobs, it is safe just to rename the
> job. Once you do, the trigger job in ep4*ILR-perf-lin64-baseline is updated
> automatically, So then when you change name of ep4*ILR-perf-lin64-baseline
> it updates trigger job in ep4*I-perf-lin64 ... etc. 
> 
> Did you try to rename jobs? Not sure if you have the right permissions to,
> but if you wanted to try the "M" and "Y" performance jobs (and you can do
> soon) then give it a try, otherwise I'll finish those up before end of day.

I tried renaming the jobs but I got a access denied message "Access Denied

slakkimsetti is missing the Create permission".

I think I cannot do this yet. I tried to rename "Job ep46YLR-perf-lin64"

Comment 3 David Williams 2016-07-11 13:27:00 EDT

I believe we are all done here. If anyone notices things missing, please open a new bug, and refer back to this one so they are connected.