|
Hi,
as agrees on last Jenkins meeting, next LTS will be based on 1.466 [1]. I identified following two critical issues needs to be backported: * JENKINS-11251 - Cannot parse coverage results Premature end of file [2] * JENKINS-13625 - ERR_CONTENT_DECODING_FAILED returned on testResults and console output after Jenkins reload [3] Please let me know if there are any other critical or blocker issues need to be backported to 1.466.1 Thanks Vojta [1] http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-06-27-18.01.html [2] https://issues.jenkins-ci.org/browse/JENKINS-11251 [3] https://issues.jenkins-ci.org/browse/JENKINS-13625 |
|
Hi Vojta,
I would like to nominate the following, new in 1.473 (2012/07/01) Updating job config.xml shouldn't clobber in-progress builds. (issue 12318) It's not a candidate yet as it hasn't been in a release for more than 2 weeks - but I'm hoping by the time the decision is taken that this would not be the case (given a new latest release is due in a few days.). /James > -----Original Message----- > From: [hidden email] [mailto:jenkinsci- > [hidden email]] On Behalf Of Vojtech Juranek > Sent: 05 July 2012 08:10 > To: [hidden email] > Subject: Backports to LTS 1.446.1 > > Hi, > as agrees on last Jenkins meeting, next LTS will be based on 1.466 [1]. > I identified following two critical issues needs to be backported: > > * JENKINS-11251 - Cannot parse coverage results Premature end of file [2] > * JENKINS-13625 - ERR_CONTENT_DECODING_FAILED returned on testResults > and console output after Jenkins reload [3] > > Please let me know if there are any other critical or blocker issues need to be > backported to 1.466.1 > > Thanks > Vojta > > [1] http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-06-27-18.01.html > [2] https://issues.jenkins-ci.org/browse/JENKINS-11251 > [3] https://issues.jenkins-ci.org/browse/JENKINS-13625 ************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the [hidden email] and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 ************************************************************************************** |
|
Hi James,
it's there more then week, so back ported. Vojta On Thursday 05 July 2012 09:28:00 Nord, James wrote: > Hi Vojta, > > I would like to nominate the following, > > new in 1.473 (2012/07/01) > Updating job config.xml shouldn't clobber in-progress builds. (issue 12318) > > It's not a candidate yet as it hasn't been in a release for more than 2 > weeks - but I'm hoping by the time the decision is taken that this would > not be the case (given a new latest release is due in a few days.). > > /James > > > -----Original Message----- > > From: [hidden email] [mailto:jenkinsci- > > [hidden email]] On Behalf Of Vojtech Juranek > > Sent: 05 July 2012 08:10 > > To: [hidden email] > > Subject: Backports to LTS 1.446.1 > > > > Hi, > > as agrees on last Jenkins meeting, next LTS will be based on 1.466 [1]. > > > > I identified following two critical issues needs to be backported: > > * JENKINS-11251 - Cannot parse coverage results Premature end of file [2] > > * JENKINS-13625 - ERR_CONTENT_DECODING_FAILED returned on testResults > > > > and console output after Jenkins reload [3] > > > > Please let me know if there are any other critical or blocker issues need > > to be backported to 1.466.1 > > > > Thanks > > Vojta > > > > [1] > > http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-06-27-18.01.html > > [2] https://issues.jenkins-ci.org/browse/JENKINS-11251 > > [3] https://issues.jenkins-ci.org/browse/JENKINS-13625 > > **************************************************************************** > ********** This message is confidential and intended only for the addressee. > If you have received this message in error, please immediately notify the > [hidden email] and delete it from your system as well as any copies. > The content of e-mails as well as traffic data may be monitored by NDS for > employment and security purposes. To protect the environment please do not > print this e-mail unless necessary. > > NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 > 4EX, United Kingdom. A company registered in England and Wales. Registered > no. 3080780. VAT no. GB 603 8808 40-00 > *************************************************************************** > *********** |
|
I also would like to backport JENKINS-14113 (from 1.472 : 4e7a43c5863b5e7ad637a5034f75d3c144c45129)
to fix github webhook 2012/7/9 Vojtech Juranek <[hidden email]> Hi James, |
|
In reply to this post by Vojtech Juranek
Hi,
backports to 1.466.1 are done, could you please create RC? For list of backports check changelog [1]. It passed all automated test (on JonJ there were actually 4 failures [2], I haven't looked very carefully on it yet, but it seems me like some environment issue, as on our instance it passes without any failure [3]) Thanks Vojta [1] https://github.com/jenkinsci/jenkins/blob/stable/changelog.html#L56 [2] http://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_lts_branch/63/ [3] https://ci.jboss.org/hudson/job/HTS-Jenkins-LTS/25/ On Thursday 05 July 2012 09:10:14 Vojtech Juranek wrote: > Hi, > as agrees on last Jenkins meeting, next LTS will be based on 1.466 [1]. > I identified following two critical issues needs to be backported: > > * JENKINS-11251 - Cannot parse coverage results Premature end of file [2] > * JENKINS-13625 - ERR_CONTENT_DECODING_FAILED returned on testResults and > console output after Jenkins reload [3] > > Please let me know if there are any other critical or blocker issues need to > be backported to 1.466.1 > > Thanks > Vojta > > [1] > http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-06-27-18.01.html > [2] https://issues.jenkins-ci.org/browse/JENKINS-11251 > [3] https://issues.jenkins-ci.org/browse/JENKINS-13625 |
|
Administrator
|
Aye aye, sir.
2012/7/9 Vojtech Juranek <[hidden email]>: > Hi, > backports to 1.466.1 are done, could you please create RC? > > For list of backports check changelog [1]. It passed all automated test (on > JonJ there were actually 4 failures [2], I haven't looked very carefully on it > yet, but it seems me like some environment issue, as on our instance it passes > without any failure [3]) > > Thanks > Vojta > > [1] https://github.com/jenkinsci/jenkins/blob/stable/changelog.html#L56 > [2] http://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_lts_branch/63/ > [3] https://ci.jboss.org/hudson/job/HTS-Jenkins-LTS/25/ > > On Thursday 05 July 2012 09:10:14 Vojtech Juranek wrote: >> Hi, >> as agrees on last Jenkins meeting, next LTS will be based on 1.466 [1]. >> I identified following two critical issues needs to be backported: >> >> * JENKINS-11251 - Cannot parse coverage results Premature end of file [2] >> * JENKINS-13625 - ERR_CONTENT_DECODING_FAILED returned on testResults and >> console output after Jenkins reload [3] >> >> Please let me know if there are any other critical or blocker issues need to >> be backported to 1.466.1 >> >> Thanks >> Vojta >> >> [1] >> http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-06-27-18.01.html >> [2] https://issues.jenkins-ci.org/browse/JENKINS-11251 >> [3] https://issues.jenkins-ci.org/browse/JENKINS-13625 -- Kohsuke Kawaguchi |
|
Administrator
|
1.466.1-rc1 tag and binaries pushed to http://mirrors.jenkins-ci.org/
2012/7/10 Kohsuke Kawaguchi <[hidden email]>: > Aye aye, sir. > > 2012/7/9 Vojtech Juranek <[hidden email]>: >> Hi, >> backports to 1.466.1 are done, could you please create RC? >> >> For list of backports check changelog [1]. It passed all automated test (on >> JonJ there were actually 4 failures [2], I haven't looked very carefully on it >> yet, but it seems me like some environment issue, as on our instance it passes >> without any failure [3]) >> >> Thanks >> Vojta >> >> [1] https://github.com/jenkinsci/jenkins/blob/stable/changelog.html#L56 >> [2] http://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_lts_branch/63/ >> [3] https://ci.jboss.org/hudson/job/HTS-Jenkins-LTS/25/ >> >> On Thursday 05 July 2012 09:10:14 Vojtech Juranek wrote: >>> Hi, >>> as agrees on last Jenkins meeting, next LTS will be based on 1.466 [1]. >>> I identified following two critical issues needs to be backported: >>> >>> * JENKINS-11251 - Cannot parse coverage results Premature end of file [2] >>> * JENKINS-13625 - ERR_CONTENT_DECODING_FAILED returned on testResults and >>> console output after Jenkins reload [3] >>> >>> Please let me know if there are any other critical or blocker issues need to >>> be backported to 1.466.1 >>> >>> Thanks >>> Vojta >>> >>> [1] >>> http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-06-27-18.01.html >>> [2] https://issues.jenkins-ci.org/browse/JENKINS-11251 >>> [3] https://issues.jenkins-ci.org/browse/JENKINS-13625 > > > > -- > Kohsuke Kawaguchi -- Kohsuke Kawaguchi |
|
Hi,
it seems that the bits are not on mirrors. When trying to download, I'm getting HTTP 404. Could you please take a look? Thanks Vojta On Thursday 12 July 2012 08:55:42 Kohsuke Kawaguchi wrote: > 1.466.1-rc1 tag and binaries pushed to http://mirrors.jenkins-ci.org/ > > 2012/7/10 Kohsuke Kawaguchi <[hidden email]>: > > Aye aye, sir. > > > > 2012/7/9 Vojtech Juranek <[hidden email]>: > >> Hi, > >> backports to 1.466.1 are done, could you please create RC? > >> > >> For list of backports check changelog [1]. It passed all automated test > >> (on > >> JonJ there were actually 4 failures [2], I haven't looked very carefully > >> on it yet, but it seems me like some environment issue, as on our > >> instance it passes without any failure [3]) > >> > >> Thanks > >> Vojta > >> > >> [1] https://github.com/jenkinsci/jenkins/blob/stable/changelog.html#L56 > >> [2] > >> http://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_lts_branch/63/ > >> [3] https://ci.jboss.org/hudson/job/HTS-Jenkins-LTS/25/ > >> > >> On Thursday 05 July 2012 09:10:14 Vojtech Juranek wrote: > >>> Hi, > >>> as agrees on last Jenkins meeting, next LTS will be based on 1.466 [1]. > >>> > >>> I identified following two critical issues needs to be backported: > >>> * JENKINS-11251 - Cannot parse coverage results Premature end of file > >>> [2] > >>> * JENKINS-13625 - ERR_CONTENT_DECODING_FAILED returned on testResults > >>> and > >>> > >>> console output after Jenkins reload [3] > >>> > >>> Please let me know if there are any other critical or blocker issues > >>> need to be backported to 1.466.1 > >>> > >>> Thanks > >>> Vojta > >>> > >>> [1] > >>> http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-06-27-18.01.htm > >>> l > >>> [2] https://issues.jenkins-ci.org/browse/JENKINS-11251 > >>> [3] https://issues.jenkins-ci.org/browse/JENKINS-13625 > > > > -- > > Kohsuke Kawaguchi |
|
Hi,
Any idea when this new LTS will appear on jenkins-ci.org ? Thanks Jorg
|
|
Administrator
|
My apologies. Mirror job needed to run. It's all fixed now. [1] http://ci.jenkins-ci.org/view/Infrastructure/job/infra_mirroring/ On 07/18/2012 10:56 PM, Jorg Heymans wrote: > Hi, > > Any idea when this new LTS will appear on jenkins-ci.org ? > > Thanks > Jorg > -- Kohsuke Kawaguchi http://kohsuke.org/ |
|
Hi,
LTS 1.466.1 RC1 seems to be done [1] (special thank to Mark Waite) and I would propose to release 1.466.1. Mark spotted serious issue [2] in git plugin. We should probably warn users not to upgrade to git-plugin 1.1.21 to avoid unwanted surprise (I guess LTS users don't upgrade also plugin so often and update of Jenkins core is probably done in conjuction with upgrading plugins). Probably some LTS release announcement on users list with summary job testing would do the job? Cheers Vojta [1] https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.466.x+RC+Testing [2] https://issues.jenkins-ci.org/browse/JENKINS-14480 On Thursday 19 July 2012 14:36:27 Kohsuke Kawaguchi wrote: > My apologies. Mirror job needed to run. It's all fixed now. > > [1] http://ci.jenkins-ci.org/view/Infrastructure/job/infra_mirroring/ > > On 07/18/2012 10:56 PM, Jorg Heymans wrote: > > Hi, > > > > Any idea when this new LTS will appear on jenkins-ci.org ? > > > > Thanks > > Jorg |
|
Administrator
|
All right, I'll get the release posted tonight. On 07/23/2012 06:44 AM, Vojtech Juranek wrote: > Hi, > LTS 1.466.1 RC1 seems to be done [1] (special thank to Mark Waite) and I would > propose to release 1.466.1. > > Mark spotted serious issue [2] in git plugin. We should probably warn users > not to upgrade to git-plugin 1.1.21 to avoid unwanted surprise (I guess LTS > users don't upgrade also plugin so often and update of Jenkins core is > probably done in conjuction with upgrading plugins). Probably some LTS release > announcement on users list with summary job testing would do the job? > > Cheers > Vojta > > [1] https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.466.x+RC+Testing > [2] https://issues.jenkins-ci.org/browse/JENKINS-14480 > > On Thursday 19 July 2012 14:36:27 Kohsuke Kawaguchi wrote: >> My apologies. Mirror job needed to run. It's all fixed now. >> >> [1] http://ci.jenkins-ci.org/view/Infrastructure/job/infra_mirroring/ >> >> On 07/18/2012 10:56 PM, Jorg Heymans wrote: >> > Hi, >> > >> > Any idea when this new LTS will appear on jenkins-ci.org ? >> > >> > Thanks >> > Jorg > -- Kohsuke Kawaguchi http://kohsuke.org/ |
|
In reply to this post by Kohsuke Kawaguchi
On 07/19/2012 05:36 PM, Kohsuke Kawaguchi wrote:
> Mirror job needed to run. It's all fixed now. > > [1] http://ci.jenkins-ci.org/view/Infrastructure/job/infra_mirroring/ The main site still lists 1.447.2 as LTS. |
| Powered by Nabble | Edit this page |
