Part1
Recently , I ran into a few cases that jenkins upgrade or plugin upgrade caused jenkins job configuration save failed.
Case1 jenkins upgrade lead to jenkins configration save failed
Soultion: Go to top right corner , click the red icon for serious problems, review it , upgrade the listed plugins to eliminate the errors.
Then go to plugin managers to upgrade all the plugins that need to upgrade
Finally, the configration save went back to normal
Case2 Jenkins configuration suddenly can't be saved, no jenkins upgrade excuted
Soultion: At this scenario , jenkins haven't beed updated , the error comes out suddenly. The cost to upgrade all the plugins is high, I thought the best way
is to find out the problematic plugin directly , instead of upgrade all the plugins.
So i creat a new job , config it according to the previous one , which configuration can't be saved , config it and save it step by step , till you can't save ,then you can
directly find the one , which caused this issue and upgrade it quickly , the issue can be resolved in a short time slot.
==================================================
Part2
Sometimes , you want to debug plugins, but don't want to uninstall them , you can disable them.
The way is very easy:
create a file named: <PLUGIN_ID>. jpi. disabled inside the folder $JENKINS_HOME/plugins
For example:
touch $JENKINS_HOME/plugins/greenballs.jpi.disabled
If you want to revert this disable , very easy , just remove this file.