Couldn't agree more. Our current Jenkins box took several days to get fully operational, and upgrading just feels like too big a risk. Especially since it's so central to the developer workflow
In my experience installing updates to Jenkins has been painless, 2.0 was no different.
I've always been afraid of updating Jenkins or the plugins because things always broke. Always.
That being said, I updated a few instances to 2.0, immediately applied all plugin updates and things kept working as before. That was a surprise. I was already prepared to spend hours trying to find why our jobs were failing. That was nice.
We have had problems but mainly with plugins. There's basically no mandatory QA process for plugins, nor is there any facility to make it obvious to an updater that an upstream change affects a downstream plugin and might break it.
In my opinion, Jenkins is a product that you really need to have a test instance for, where you either have copies of your builds or you've set up some 'unit test'-type builds to exercise functionality you depend on.
Thanks for the two parent comments for relaying their experience. I'll keep it in mind should I need to upgrade this box.
I was already prepared to spend hours trying to find why our jobs were failing.
Yeah, that's exactly what I'm not prepared for, and trying to avoid. :-) No one pays the little Mac Mini on my desk much mind...until it doesn't work.
That's not to poo-poo the hard work that obviously went into this release. Big, shiny new stuff there, and the next Jenkins box I setup will be running 2.0. But for my particular situation at this point in time, it'll be 1.6 for a while.