2012/10/25 Vojtech Juranek <[email protected]> > FYI: on JonJ there are some failed tests because of time out [1], on our > instance it passed without any failure [2], so there shouldn't be any > regressions caused by backporting > > [1] > https://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_lts_branch/75/ > [2] http://ci.jboss.org/hudson/job/HTS-Jenkins-LTS/31/
https://jenkins.ci.cloudbees.com/job/core/job/jenkins_lts_branch/23/<https://jenkins.ci.cloudbees.com/job/core/job/jenkins_lts_branch/21/>also has some tests to fail on TO, even with -Dmaven.junit.timeout=600 , so I wonder there is some unpredictability here > > > On Tuesday 23 October 2012 12:10:02 Kohsuke Kawaguchi wrote: > > I'm flying back to home today, and planning to take a sweep Tuesday > > afternoon. > > 2012/10/22 Vojtech Juranek <[email protected]>: > > > Hi, > > > as agreed on the last Jenkins meeting [1], next LTS will be based on > > > 1.480. > > > I identified and backported following bug fixes: > > > > > > JENKINS-13336 Invalid JSON is produced during remote api operations [2] > > > JENKINS-14667 java.io.InvalidClassException [3] > > > JENKINS-15277 Check view permissions before showing config page [4] > > > JENKINS-15493 Excessive memory usage with large number of request > threads > > > [5] > > > > > > Please let me know by Tuesday if there are any other critical or > blocker > > > issues need to be backported to 1.480.1. As also agree on the meeting, > RC > > > should be available by Wednesday. > > > > > > Thanks > > > Vojta > > > > > > [1] > > > > http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-10-17-18.02.html > > > [2] https://issues.jenkins-ci.org/browse/JENKINS-13336 > > > [3] https://issues.jenkins-ci.org/browse/JENKINS-14667 > > > [4] https://issues.jenkins-ci.org/browse/JENKINS-15277 > > > [5] https://issues.jenkins-ci.org/browse/JENKINS-15493 >
