|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Daniel Beck I think it is probably a pretty common work flow scenario. Especially in a CI env (project dedicated to a team feature branch that frequently refreshes from trunk). Anytime we dedicate projects to specific SVN branches, which we do for major features and all releases, this becomes an issue since those types of branches will refresh from trunk often. This is what worries me about the next few weeks when we branch for our next release. Our first build is going to be fine, but subsequent builds that refresh partially from trunk will undoubtedly fail. Not going to be a good time for me.