Process to move from a new release of Jenkins(1.529) to LTS 1.509

[Kishore RP]

Since we are seeing lot of issues on channel closed exceptions and slaves going offline on our main line release adoption of Jenkins which is 1.529, we want to move to LTS release 1.509, which i presume would be a lot stable.

We are having a lot of critical jobs and the down time has to be very very minimal, any suggestions on how to go about the same?

[Stephen Connolly]

I am 99.999% certain you are hitting JENKINS-18836, JENKINS-18879, JENKINS-19619.

The root cause was fixed in 1.536 and was backported to the latest LTS release 1.532.1

I would recommend using the latest LTS, i.e. 1.532.1 and not the 1.509 line

On 3 December 2013 13:19, Kishore RP <kisho...@gmail.com> wrote:

Since we are seeing lot of issues on channel closed exceptions and slaves going offline on our main line release adoption of Jenkins which is 1.529, we want to move to LTS release 1.509, which i presume would be a lot stable.

We are having a lot of critical jobs and the down time has to be very very minimal, any suggestions on how to go about the same?

--
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 jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Kishore RP]

We are seeing jenkins 12235 pretty regularly....any thoughts on when it will be fixed....

https://issues.jenkins-ci.org/browse/JENKINS-12235

You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/iJ4lSmcRal4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.

[Kishore RP]

Also , all our slaves are windows OSs, slaves invoked via jnlp,
12235 is almost giving us sleepless nights at times:-( .

[Oleg Nenashev]

Hello Kishore,

I've tried the backward migration from 1.532.1-rc to 1.509.4 several days ago (just to have an evacuation plan).
Such migration is possible if you have no plugin dependency issues. Anyway, it requires manual configuration changes, hence you definitely need a mirror server to provide a short downtime.  
You can also experience painful issues with multi-configuration projects (JENKINS-7825, JENKINS-7285, etc.).

In general, I agree with Stephen.
Forward migration to the next LTS is a best way if it is applicable to your needs.
BTW, any new LTS contains too much newly introduced issues, so it is a common practice to wait for x.2 or x.3 releases if you want to migrate between LTS branches.

Best regards,
Oleg Nenashev

вторник, 3 декабря 2013 г., 20:51:13 UTC+4 пользователь Kishore RP написал:

[Kishore RP]

Thank you Oleg Nenashev and Stephen

We will move ahead with LTS 1.532