|
||||||||
|
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.
I'm clearly seeing this issue with Jenkins 1.549.
I'm using multiple hg repositories. I trigger the build by polling for changes to any one of the repositories. This polling works fine and the changes are correctly reported by the Jenkins build instance dashboard and the changes do correctly appear in the workspace.
However, the console log always reports "no changes found" and gives the revision information appropriate to the previous build. FWIW, if I subsequently manually trigger a build, then the manually triggered build reports the updated revision(s) (of course, as always, "no changes found").
Update:
Installed Jenkins 1.554.1 on RHEL 6.5 server. Still seeing this issue.