-
Bug
-
Resolution: Unresolved
-
Major
-
None
After an upgrade Jenkins silently removed hudson.plugins.parameterizedtrigger.BlockableBuildTriggerConfig sections from some jobs. It costed a lot of time to find this change, because it is not easily tracked.
Desired behavior: forbid Jenkins to touch the jobs at all during upgrade, let them simply fail even if something is wrong with the plugins.
Why: because for me it is much more easy to see the job red or not loadable at all than search what and where Jenkins silently modified. Looking at "/jobConfigHistory" of all of jobs is absolutely inconvenient if you have hundreds of jobs.
Can you please make a global configuration option to forbid Jenkins modifying jobs config.xml even if it will cause not working jobs?