|
||||||||
|
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.
I was able to duplicate the behavior reported here.
I assume that the message "No new revisions were found; the most-recently built branch will be built again" is relevant to this case. I assume that since the plugin decided there were no changes on any branches, it built the last branch again, rather than applying the selected inverse branch choosing strategy.
The steps I took:
After that sequence of verification steps, I then submitted a change to the master branch while the inverse choosing strategy was enabled. I did not expect any build, since the change was to the branch which should have been excluded by the "Inverse" choosing strategy. I was surprised. It built and reported that there were no changes so it was buidling the same version again. I assume that is because the fast remote polling does not support the inverse branch choosing strategy.
I added "Force polling with workspace" and submitted another change to the master branch. That did not cause a build. I submitted a change to another branch, and that caused a rebuild. It appears "Force polling with workspace" may need to be implicitly enabled if the inverse branch choosing strategy is enabled.