Releases

[Ugo Bellavance]

Hi,

I'm sorry, I didn't really follow the recent news about the changes in Jenkins' releases but I have done some reading and I still can't find an answer.

Without knowing that there was an LTS version at 1.651, we upgraded our Jenkins system to what yum gave us: 1.656.

Now we're experiencing problems (https://groups.google.com/forum/#!searchin/jenkinsci-users/resources/jenkinsci-users/qLwBFyQ84Z4/GWP4Ve_jOAAJ) and we don't know what are the options.  From what I can see, one can:

• Stick to 1.651 and get only fixes (1.651.2, 1.652.3, etc.)
• Keep using the current release and get version 2.x
• Be in the fog like us and wonder why there are still releases in 1.x in the current branch after 1.651

I saw this morning that 1.657 and 1.658 were out, so I downloaded the rpms and ran an rpm -qp --changelog on them to find out that this is not really used. Well, it redirects the user to the online changelog (http://jenkins-ci.org/changelog). However,  there is nothing for 1.657 or 1.658 in either the current or LTS release changelog.  All I can find about these releases is on github: [maven-release-plugin] copy for tag jenkins-1.658. Is that an artificial bump in the version by some automated component?  If only someone could tell me if I could downgrade to 1.651 from 1.656 that would help.

Thanks,

[Daniel Beck]

> On 16.05.2016, at 17:15, Ugo Bellavance <ug...@lubik.ca> wrote:
>
> However, there is nothing for 1.657 or 1.658 in either the current or LTS release changelog. All I can find about these releases is on github: [maven-release-plugin] copy for tag jenkins-1.658. Is that an artificial bump in the version by some automated component? If only someone could tell me if I could downgrade to 1.651 from 1.656 that would help.
>

These were test releases since we performed some changes to the release process right before 2.0 came out. They have no notable changes (one change was implemented towards 1.657 and then reverted towards 1.658).

See the diff between 1.656 and 1.658, the only real (but still very minor) change is highlighted:
https://github.com/jenkinsci/jenkins/compare/jenkins-1.656...jenkins-1.658#diff-e489e4f9a21586cacd9342ff6eeded61R31

Just ignore them, like the changelog does ;-)

[Ugo Bellavance]

 Ok, but how can I apply a fix then? I've been told that my problem may be caused by JENKINS-34213, this currently has a status of "Fixed".  How can I update my code to have the fix?

Thanks,

Ugo

[Daniel Beck]

> On 17.05.2016, at 13:57, Ugo Bellavance <ug...@lubik.ca> wrote:
>
> Ok, but how can I apply a fix then? I've been told that my problem may be caused by JENKINS-34213, this currently has a status of "Fixed". How can I update my code to have the fix?
>

It's in Jenkins 2.4. The fix is not yet available on the LTS release line.

[Ugo Bellavance]

Ok, that is great, but when it will be available on the LTS line, will I be able to update my install from 1.656 to the version that will contain the fix (1.651.3 I guess)?  Is there a way to be sure that JENKINS-34213 is the problem that I hit?  I do have a heap dump and I've done some analysis on it, but it's a bit too complex for me at this point.  Should I put the dump somewhere and ask for it to be analyzed in JENKINS-34213?

Thanks,

[Daniel Beck]

> On 17.05.2016, at 21:33, Ugo Bellavance <ug...@lubik.ca> wrote:
>
> Ok, that is great, but when it will be available on the LTS line, will I be able to update my install from 1.656 to the version that will contain the fix (1.651.3 I guess)?

It has been nominated for back porting, the rest is decided by the LTS team (aka Oliver :-) ). They may include it in 1.651.3, they may not, depending on the risk expected for this change.

I expect that going from 1.656 to 1.651.x should be possible without major hassle, as AFAIK there have not been incompatible changes in on-disk data formats, but, as always, backup everything, and (if downtime is unacceptable), do it in a staging environment first.

> Should I put the dump somewhere and ask for it to be analyzed in JENKINS-34213?

No. Our JIRA is an issue tracker, not a support site. You could upload it somewhere and ask for opinion here, but if I were you I wouldn't hold my breath for an answer.