Issue Type: Bug Bug
Assignee: Mirko Friedenhagen
Components: jobconfighistory
Created: 03/Jul/12 10:03 PM
Description:

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!

Project: Jenkins
Priority: Minor Minor
Reporter: Patrick Connolly
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to