Hi Sarah,

I think this is a matter of trial and error as also the plugins used deal a 
great impact on your Jenkins installation.
Take a look at http://dl.aragost.com/jenkins/war-stable-rc or also the 
parent folder. I think that's what you actually are looking for.

Take care
Jan

Am Donnerstag, 19. Juli 2012 22:42:10 UTC+2 schrieb Sarah Woodall:
>
> Could someone please advise me? I am setting up a new Windows 7 machine 
> as our new Jenkins server. We have lots of jobs already defined, which 
> we ran successfully on an old machine (also Windows 7) using Jenkins 
> 1.441. 
>
> I need to know which release of Jenkins I can install on the new machine 
> and safely use. 
>
> Here are my problems: 
>
> 1. I know I can't use the latest release (Jenkins 1.474), because I need 
> to use multi-configuration jobs. So the bug that I found and reported a 
> couple of days ago (Jenkins JIRA issue 14474) rules this out. 
>
> 2. I know I must not go back to the old release we were using on our old 
> machine (Jenkins 1.441), even though our jobs do work on it, because of 
> the security advisory that was issued in March: 
> > This affects all the releases of Jenkins to date (main line releases up 
> > to 1.452 and LTS up to 1.424.3.) Please upgrade to the new releases at 
> > your earliest convenience 
>
> So ideally I need to know when bug 14474 was introduced, and go back to 
> the release just before that (assuming it is later than 1.452). If it 
> was before 1.452, though, then that isn't an option. 
>
> Or, alternatively, can anyone advise me when a fix for 14474 is likely 
> to appear? According to the comment by Matthew Cooper in the JIRA 
> report, something that sounds like the same bug is already fixed on the 
> trunk. I thought perhaps I could download the latest release candidate 
> and try it out, but there isn't one available. Clicking on the "RC" link 
> on the Jenkins downloads page leads me to: 
> > The requested URL /pub/jenkins/war-rc/1.475/jenkins.war was not found on 
> this server. 
>
> If I knew there was only a short time to wait before I had a fix for 
> that bug, I'd probably wait. 
>
> Or is there anything I can do to help? Perhaps I could test the fix, if 
> indeed it has already been fixed? 
>
> Thanks for listening! I'd be so grateful for good advice over this 
> problem. 
> -- 
> Sarah Woodall 
> Code Red Technologies 
>

Reply via email to