-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
Job Configuration History Plugin 2.16
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?
[JENKINS-45821] JobConfigHistory is flooded by pipeline steps
Daniel Geißler
created issue -
Daniel Geißler
made changes -
| Environment | New: Job Configuration History Plugin 2.16 |
| Component/s | Original: lockable-resources-plugin [ 18222 ] | |
| Component/s | Original: pipeline-milestone-step-plugin [ 21448 ] |
Allan BURDAJEWICZ
made changes -
| Remote Link | New: This issue links to "PR#74 (Web Link)" [ 20789 ] |
Allan BURDAJEWICZ
made changes -
| Remote Link | New: This issue links to "PR#65 (Web Link)" [ 20790 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |