|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
well for me the config.xml of the jobs was the killer. the disk usage plugin adds what appears to be a timestamp everytime it calculates (which seemed to be with each build). so 50+ jobs building 10 times a day turned into 500 commit messages which was a lot of noise...![]()
being able to filter out 'system' commits would be quite handy as all these changes were made by 'the system'. or queing up system commits to a daily (or whenever a real person makes a real change to the job).. anything![]()