Backporting for 1.642.2 done

22 views
Skip to first unread message

Oliver Gondža

unread,
Feb 4, 2016, 12:31:30 PM2/4/16
to jenkin...@googlegroups.com, kkawa...@cloudbees.com
Hi,

The backporting is done. We are ready for the RC.

One issue rejected:
https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%201.642.2-rejected
Most issues backported:
https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%201.642.2-fixed

--
oliver

Oleg Nenashev

unread,
Feb 16, 2016, 4:00:37 PM2/16/16
to Jenkins Developers, kkawa...@cloudbees.com
Hi,

We discovered one binary compatibility issue during the testing:
Needs to be fixed in 1.642 IMHO

четверг, 4 февраля 2016 г., 20:31:30 UTC+3 пользователь ogondza написал:

Oliver Gondža

unread,
Feb 17, 2016, 5:01:52 AM2/17/16
to jenkin...@googlegroups.com
On 02/16/2016 10:00 PM, Oleg Nenashev wrote:
> Hi,
>
> We discovered one binary compatibility issue during the testing:
>
> * Class: jenkins.util.groovy.GroovyHookScript
> * Issue: https://issues.jenkins-ci.org/browse/JENKINS-32985
> * Fix: https://github.com/jenkinsci/jenkins/pull/2035
>
> Needs to be fixed in 1.642 IMHO

Nice catch! I am thinking what we can do to detect those more reliably.
Running plugin-compat-tester against a set of most popular plugins seems
to be the minimum.

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