Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-45821

JobConfigHistory is flooded by pipeline steps

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • jobconfighistory-plugin
    • 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

          Andrew Bayer added a comment -

          Yup, since those steps use JobProperty implementations and the like, they technically do change the configuration of the job. Perhaps JobConfigHistory needs to filter them.

          Andrew Bayer added a comment - Yup, since those steps use JobProperty implementations and the like, they technically do change the configuration of the job. Perhaps JobConfigHistory needs to filter them.

          Jochen A. Fürbacher added a comment -

          Fixed in 2.20.

          Jochen A. Fürbacher added a comment - Fixed in 2.20.

            stefanbrausch Stefan Brausch
            dageissl Daniel Geißler
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: