[
https://issues.jenkins-ci.org/browse/JENKINS-13033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160060#comment-160060
]
Zac Campbell commented on JENKINS-13033:
----------------------------------------
Just discovered "Do not save duplicate history"
My apologies..
> History record created when no changes were made
> ------------------------------------------------
>
> Key: JENKINS-13033
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13033
> Project: Jenkins
> Issue Type: Improvement
> Components: jobconfighistory
> Reporter: Zac Campbell
> Assignee: Mirko Friedenhagen
> Priority: Minor
>
> We've found that when modifying Jenkins jobs some of our users are making the
> changes, clicking Apply and then Save. Jenkins allows you to do this - it
> doesn't disable the buttons depending upon whether fields have changed.
> jobConfigHistory plugin triggers and saves a change record for each of the
> Apply and Save action. Usually the latter has no changes in the diff.
> While this isn't a bug the extra empty records muddy the history and are not
> beneficial, take up space.
> Suggest that jobConfigHistory could detect when no changes were made and not
> add a change record. Alternatively Jenkins would need validation on the
> Save/Apply buttons.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
