On 09.03.2015, at 18:22, Les Mikesell <lesmikes...@gmail.com> wrote:

> Yes, when you know that LTS is going to screw up data, it only seems
> reasonable to post it in a visible place.

The data was "screwed up" by the regular weekly release, and that was mentioned:

- On the /manage page after the upgrade
- In the changelog, in bold
- In the Jenkins log

Complete with instructions how to revert it.

> So when an issue affecting it becomes
> known, the ideal thing would be to _fix_ the by-then-known problem,
> but if that is too much to ask, warning about it would seem
> appropriate.

There is no "issue affecting it". Again: You get the documentation on the 
backwards-compatibility-breaking change to build layout when you upgrade. It's 
not like there's a path to get into this situation where you're never shown any 
information about this change. It's shown earlier than relevant in this case, 
but if you ever read it, you'll understand that downgrading is more effort than 
usual.

I think the basic misunderstanding is that think you can move from any Jenkins 
version to any other Jenkins version at will, when only upgrades to higher base 
versions are effectively supported. At least that's what I gather from:

> Yes, exactly.  Would you not want to know that before installing the
> latest LTS which is known to cause this issue?  In fact it seems
> somewhat odd to introduce this scenario without considering the effect
> on people switch to LTS - which I'd expect to be a likely situation.

Here's the generally supported upgrade paths:
Jenkins 1.XXX -> Jenkins 1.YYY (YYY > XXX): OK!
Jenkins 1.XXX -> Jenkins 1.YYY.z (YYY > XXX): OK!
Jenkins 1.XXX.w -> Jenkins 1.YYY.z (YYY > XXX): OK!
Jenkins 1.XXX -> Jenkins 1.XXX.y: OK!

Going from LTS to a (much) more recent weekly generally works as well, but 
there may be exceptions.

Downgrading often comes with data loss or other incompatibilities (e.g. 
detached plugins that won't work with the downgraded core), so I don't think 
this is supported. Couldn't find any reference on it though.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/307FC5F6-8E01-4BE8-9EC1-38A2AE1D7BE9%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Reply via email to