Oh, thanks Uwe, I hadn’t looked at Jenkins yet today :)

I’ll recreate the 5.5 jobs as you suggest on ASF Jenkins (and disable them), 
and leave the smoker job fixups to you.

--
Steve
www.lucidworks.com

> On Mar 3, 2016, at 11:51 AM, Uwe Schindler <[email protected]> wrote:
> 
> Hi,
> 
> Sorry, the 5.x ones are already gone! I touched and cleaned up every Jenkins 
> Job today (trunk -> master). I also added the 6.x Jobs.
> To recreate the 5.5 Jobs you have to clone a 6.x Job, but don't forget to 
> change the JVM from "latest1.8" to "latest1.7". The Smoker Job is more 
> complicated, because it checks both JVMs, but I can set that up again - there 
> is a plugin for that.
> 
> The 5.5 jobs are still running on Policeman Jenkins, so it is not urgent.
> 
> Uwe
> 
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: [email protected]
> 
> 
>> -----Original Message-----
>> From: Steve Rowe [mailto:[email protected]]
>> Sent: Thursday, March 03, 2016 5:39 PM
>> To: Lucene Dev <[email protected]>
>> Subject: Dropping branch_5x Jenkins jobs
>> 
>> Assuming there won’t be a 5.6 release, we should drop the 5.x jobs on
>> Jenkins, and disable but keep around the 5.5 jobs, to be used for a 5.5.1
>> release.
>> 
>> FYI, I removed the 5.5 jobs from ASF Jenkins a couple days ago (accidentally
>> for the first one, intending to just disable, but after I removed the first 
>> one I
>> just continued down that path…), but these are easy enough to clone from
>> the existing branch_5x jobs.
>> 
>> Thoughts?
>> 
>> --
>> Steve
>> www.lucidworks.com
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to