|
||||||||
|
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/groups/opt_out.
At this point requiring 1.4+ is probably reasonable. Still unclear to me that revsets are the appropriate fix for this issue, since there is no test case; historical branch names should not really matter since what the plugin cares about is whether the last built revision is distinct from the current expansion of the target revision, which ought to be using the current definition of the branch. (Check behavior against 1.50-beta-1 which added tag support.)