|
||||||||
|
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-14138) New git branch has emp... [email protected] (JIRA)
- [JIRA] (JENKINS-14138) New git branch ha... [email protected] (JIRA)
- [JIRA] (JENKINS-14138) New git branch ha... [email protected] (JIRA)
- [JIRA] (JENKINS-14138) New git branch ha... [email protected] (JIRA)
- [JIRA] (JENKINS-14138) New git branch ha... [email protected] (JIRA)
- [JIRA] (JENKINS-14138) New git branch ha... [email protected] (JIRA)
- [JIRA] (JENKINS-14138) New git branch ha... [email protected] (JIRA)
- [JIRA] (JENKINS-14138) New git branch ha... [email protected] (JIRA)
- [JIRA] (JENKINS-14138) New git branch ha... [email protected] (JIRA)

Assume the following:
A--
B--C topic/
D--
E-F--G masterThe last build was of E. I push the branch topic to the server and it is built. I would expect the changeset for this build to contain A, B, C. Instead it's empty. My commit hook script sends me email that these are the new changes, I would expect my CI system to do the same and notify the committers of A, B and C if those changes passed CI.