While investigating https://issues.jenkins-ci.org/browse/JENKINS-45506 i've encoutered tons of saved configuration changes due to pipeline step serializations.

Now that i know, i can configure around this, but it seems generally a bad idea to store data in the history that changes multiple times on every build a pipeline step is involved.

Basically two pipeline steps are flooding our history:

• org.jenkinsci.plugins.pipeline.milestone.Milestone
• org.jenkins.plugins.lockableresources.LockableResourcesManager

Maybe these plugins should be added to the default pattern, some hints should be put into their documentation or even a new api to distinguish regular configuration changes from simple status updates may be introduced?