
Recently I had to perform an upgrade for Jenkins and it was as dead simple as replacing a .war file and I was err.... DONE! All I did was stopped and started the process whilst replacing the war file. Once I rebooted, it all just worked. They seriously think about making their installations to run the latest software which I personally consider a true value.
Anyways, the reason me posting this is to help my fellow developers who are running into an issue where their slave would not start up after the upgrade process.
You would face an error something like this below when you go and inspect in the slave agent.
This was how the overall upgrade felt like :)
Cheers!
Braga
No comments:
Post a Comment