Mark Waite commented on Bug JENKINS-21264

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:

  1. Create a new freestyle project
  2. Configure it to use Git as SCM with a nearby git:// protocol repository
  3. Add the branch choosing strategy, set it to "Inverse"
  4. Add an SCM poll every two minutes setting to the job
  5. Save the job - Confirm the job ran multiple times, once for each branch not named "master"
  6. Modify the branch choosing strategy to default
  7. Run the job - confirm it builds the master branch
  8. Modify the branch choosing strategy to Inverse
  9. Run the job - confirm it incorrectly builds the master branch again
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.

Reply via email to