|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-14568) Improve commit messages f... [email protected] (JIRA)
- [JIRA] (JENKINS-14568) Improve commit messages f... [email protected] (JIRA)
- [JIRA] (JENKINS-14568) Improve commit messages f... [email protected] (JIRA)
- [JIRA] (JENKINS-14568) Improve commit messages f... [email protected] (JIRA)
- [JIRA] (JENKINS-14568) Improve commit messages f... [email protected] (JIRA)
- [JIRA] (JENKINS-14568) Improve commit messages f... [email protected] (JIRA)
- [JIRA] (JENKINS-14568) Improve commit messages f... [email protected] (JIRA)
- [JIRA] (JENKINS-14568) Improve commit messages f... [email protected] (JIRA)
- [JIRA] (JENKINS-14568) Improve commit messages f... [email protected] (JIRA)
- [JIRA] (JENKINS-14568) Improve commit messages f... [email protected] (JIRA)
- [JIRA] (JENKINS-14568) Improve commit messages f... [email protected] (JIRA)
- [JIRA] (JENKINS-14568) Improve commit messages f... [email protected] (JIRA)
- [JIRA] (JENKINS-14568) Improve commit messages f... [email protected] (JIRA)

Yup this is a limitation of the "transactional commit" feature : It's hard for me to identify a "transaction" when it comes from the SYSTEM (that is, automated modification made by jenkins, in the background).
I think it should be better handled during a "human" modification (because in that case, 1 http request = 1 scm transaction).
I don't know if you can modify multiple module configurations during 1 http request (I don't have multimodules on my current instance), but if you can, I think there will only be 1 commit.