|
||||||||
|
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/d/optout.
Hi, Mark,
Yes, I can test out the 1.10.0 plugin. However, after reading your explanation, I still do not understand why Jenkins triggered build the festivus-dev branch when changes were checked into master, not either festivus-dev branch. Also, builds were triggered even when there was a typo in the branch name. It seems like the existence of the 2nd festivus-dev branch caused Jenkins to completely ignore the branch specifier and trigger all builds regardless of the branch they were configured with. Even if both "jdoe/blah/festivus-dev" and "festivus-dev" , a change checked into "master" should not have triggered a build.