The planned behavior of JENKINS-13613 sounds perfect.

Current issue JENKINS-14568 is still needed: even with JENKINS-13613, I'll have tens of changesets with the same message (or emails within the same thread: one thread per user).
Thinking about the job name, the file paths are always of the form jobs/jobName/.../someFile.xml (when configuring jobs) so you could split on slashes ("/") and extract the word after jobs to get the job name.
When there is not such a pattern, that means the configuration change wasn't done on a job but on a global config and so the whole file path is nice in that case.

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