Definite regression over 1.565.2 (introduced in 1.565.3) which is now reported by users and causes a loss in functionality.
https://issues.jenkins-ci.org/browse/JENKINS-25340. I do not coniser the scenario that causes this to happen to be an edge case (it is normal for builds to be aborted). Whereas having lots of build history and slow disks is an edge case (hence why it took from introducing lazy builds for it to be reported vs a short amount of time for that "fix" to be reported as causing a regression). On Tuesday, 28 October 2014 11:00:02 UTC, ogondza wrote: > > Hi, LTS RC testing is on. > > Bits are on usual location: > http://mirrors.jenkins-ci.org/war-stable-rc/latest/jenkins.war > So does test plan: > https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.580.x+RC+Testing > > Sorry for the late notice > -- > oliver > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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.
