I was looking at this over the weekend to see if the risk&#x2F;benefit ratio was appropriate for our team. Meh, we already use the pipelines plug-in, and the insecure-by-default configuration has already been locked down, so for our team the answer is, &quot;no, it&#x27;s not worth risking mikestew having to spend a day putting things back the way they were if the upgrade goes horribly wrong&quot;. I&#x27;m supposed to be writing code, not dicking around with broken installs.<p>That&#x27;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&#x27;ll be 1.6 for a while.