|
||||||||
|
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.
I don't understand how we would detect the difference in the git plugin between "shortly after job creation" and long term running behavior. If a previously unknown branch is detected, and if that branch matches the wildcard provided in "Branches to build", then that branch will be scheduled to build. If we insert a heuristic for the age of the branch, then we will have some users complaining about the heuristic being the wrong value, or we must prompt for them to enter a "branch age" value into the plugin. Both seem like it is a "can't win" situation. The user doesn't know the value to use, and any branch age value we choose will be wrong for some set of users.