Hi I've been a administering Jenkins for about 2 - 3 years now. What I've come across several times is that while updates to the Jenkins core go fairly smoothly, the plugins update don't. After the recent security related mandatory update from 2.40 -> 2.45, while the core behaves fine, a plugins update screwed stuff up. Fortunately, from my previous experiences, I had made a backup of the plugins folder and was able to get back to where I was without the issues nor the updated plugins.
There were some 20 + plugins that needed an update and I chose to update all of them. I(and others I'm sure) don't have the time or patience to update each one, wait for a week, and declare it a success. What is the most common strategy to update plugins? Should I create a scm repo and checkin each time I apply an update so I can go back to the one that was working fine? Even so, some issues might come up after weeks. The recent issue I had was garbage messages like 'could not connect to remote host' eventhough everything was working fine. There was no indication that a certain plugin's update could have caused this. In one scenario, a rolling back of the git plugin solved a issue. thanks -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7ea14bbd-9134-4786-9472-afcb234fcd18%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
