Re: Upgrade from 1.526 -> current: pitfalls?

2014-09-15 Thread Jamie Lawrence
On 9/15/14, 2:27 PM, "Daniel Beck" wrote: >Generally, if you prefer rarely updating Jenkins, the LTS would be a >better choice. Four major releases per year, with two bugfix releases for >each of them. [...] Thanks for the information - that¹s a really very handy list. I do appreciate it. -

Re: Upgrade from 1.526 -> current: pitfalls?

2014-09-15 Thread Daniel Beck
Generally, if you prefer rarely updating Jenkins, the LTS would be a better choice. Four major releases per year, with two bugfix releases for each of them. - Jenkins uses Jetty as default container (when running `java -jar jenkins.war`) since 1.535, resulting in possible issues with very large

Re: Upgrade from 1.526 -> current: pitfalls?

2014-09-15 Thread Jamie Lawrence
> I'm not aware of problematic changes in that range. I've preferred to stay on > the LTS version because it gets more testing, has longer time between > updates, and is only constructed after some time of people "test driving" > various of the "cutting edge" versions. Thanks for the explanation.

Re: Upgrade from 1.526 -> current: pitfalls?

2014-09-15 Thread Mark Waite
On Mon, Sep 15, 2014 at 3:08 PM, Jamie Lawrence wrote: > > > If the system has not been upgraded in that long, you should probably > consider > > using the long term support release (LTS) instead of upgrading to the > latest tip > > of development. > > Is that because this particular system

Re: Upgrade from 1.526 -> current: pitfalls?

2014-09-15 Thread Jamie Lawrence
> If the system has not been upgraded in that long, you should probably consider > using the long term support release (LTS) instead of upgrading to the latest > tip > of development. Is that because this particular system does not seem to get enough attention, or because there are changes in b

Re: Upgrade from 1.526 -> current: pitfalls?

2014-09-15 Thread Mark Waite
If the system has not been upgraded in that long, you should probably consider using the long term support release (LTS) instead of upgrading to the latest tip of development. Mark Waite On Mon, Sep 15, 2014 at 2:59 PM, Jamie Lawrence wrote: > Hi all, > > I¹ve inherited a Jenkins install that (

Upgrade from 1.526 -> current: pitfalls?

2014-09-15 Thread Jamie Lawrence
Hi all, I¹ve inherited a Jenkins install that (to my naïve eyes) looks pretty straightforward. It is 1.526, few plugins, Centos environment. Going through the Wiki and poking around Google, I¹m not seeing anything indicating much in the way of upgrade pain in going from 1.526 to 1.580, aside from