[JIRA] (JENKINS-14568) Improve commit messages from SCM Sync Configuration

Wed, 25 Jul 2012 05:57:31 -0700

The file path is enough (and contains the job's name).
It would be really useful: I'm working with about 400 jobs (https://qa.nuxeo.org/jenkins/). With so much jobs, developers need the ability to configure jobs themselves, even if I may have to review them latter. I setup an email notification on the Git repository dedicated to SCM Sync Conf (but the readability issue is also true when directly looking at the repository commits history). Because of the current generic message, I cannot quickly review changes: the commits history gives no information and the emails are all threaded together per user (since it's the only information which varies); I have to look at the details for every commit to know which job is involved, that allows unperceived changes on sensible jobs.

If I properly understood JENKINS-13613, it will still build a changeset per file/job gathering related Saveable objects instead of generating a commit per object. So it doesn't collide with the current issue: we'll still need to distinguish changesets thanks to their commit message and the related file will be the same for a given changeset (as you wrote: << A Changeset will be made of a Map<filePath, contentOfFile>. Thus, if multiple Saveable work in the same file, they will override same Changeset entry each time the Saveable is saved.>>).
What do you mean with << several modification changes on several files = 1 commit >> ? If I misunderstood and you plan to build a unique changeset for multiple changes on multiple jobs, I guess it makes no sense and reduces readability: what about if we need to revert some change on a job or if some people are responsible of reviewing changes on a given group of jobs? Avoiding multiple commits for a single change on a given job is a nice improvement though.
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