Jenkins 2.89.1 LTS RC testing started

76 views
Skip to first unread message

Oliver Gondža

unread,
Nov 23, 2017, 4:58:04 AM11/23/17
to jenkin...@googlegroups.com
Hello everyone,

Latest LTS RC was made public and it is ready to be tested. Release is
scheduled for 2017-12-06.

Report your findings in this thread or on the test plan wiki page.

Download bits from
http://mirrors.jenkins-ci.org/war-stable-rc/2.89.1/jenkins.war
Check community maintained LTS test plan
https://wiki.jenkins-ci.org/display/JENKINS/LTS+2.89.x+RC+Testing

Thanks
--
oliver

Patrick van Dissel

unread,
Nov 23, 2017, 5:20:39 AM11/23/17
to Jenkins Developers
Where can I find the changelog of this LTS RC release?

Daniel Beck

unread,
Nov 23, 2017, 6:44:26 AM11/23/17
to Jenkins Developers

> On 23. Nov 2017, at 11:20, Patrick van Dissel <pvdi...@gmail.com> wrote:
>
> Where can I find the changelog of this LTS RC release?

https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.89.1-fixed are the backported fixes.

Besides that, there's no user changelog (or upgrade guide) yet, it'll be written some time in the next two weeks.

Daniel Beck

unread,
Nov 29, 2017, 9:33:29 AM11/29/17
to jenkin...@googlegroups.com

> On 23. Nov 2017, at 12:44, Daniel Beck <m...@beckweb.net> wrote:
>
> https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.89.1-fixed are the backported fixes.

We missed https://issues.jenkins-ci.org/browse/JENKINS-47909 because it was kept open.

https://github.com/jenkinsci/jenkins/commit/7c06a9ba946800151c5d9fc38793ac4bbd3fea5f seems reasonably straightforward, could we still include this? WDYT?

Jesse Glick

unread,
Nov 29, 2017, 9:53:34 AM11/29/17
to Jenkins Dev
On Wed, Nov 29, 2017 at 9:33 AM, Daniel Beck <m...@beckweb.net> wrote:
> We missed https://issues.jenkins-ci.org/browse/JENKINS-47909 because it was kept open.

Oops, my fault for not double-checking JIRA after seeing that the PR was merged.

> https://github.com/jenkinsci/jenkins/commit/7c06a9ba946800151c5d9fc38793ac4bbd3fea5f seems reasonably straightforward, could we still include this?

I would recommend backporting it at least to .2 if it is too late for
.1. The fix seems rather safe, and for those users affected by the bug
the regression was pretty serious. (Yes there was a workaround, but
you would need to find it, and in the meantime you have a complete
service outage.)

Oliver Gondža

unread,
Nov 30, 2017, 10:41:58 AM11/30/17
to jenkin...@googlegroups.com
I have squeezed it into .1 (since you guys have vouched for the fix) and
will keep it there iff automated tests will go fine.

--
oliver
Reply all
Reply to author
Forward
0 new messages