Config changes are logged even when job saved with no changes

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Wasn't sure whether this was a bug or by design, but would it not make more sense to only log changes when the config files has actually been altered (as opposed to simply saved)?

      Not such a large concern when all changes are made by people, but when using a plugin that alters config.xml programmatically, lots of noise can accumulate in the change log. In particular, the build description setter plugin saves the job configs on each run.

      Thanks!

            Assignee:
            Stefan Brausch
            Reporter:
            Patrick Connolly
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: