same issue here.
git-client-plugin 1.6.2
build-flow-plugin 0.10

/job/builds.core.master.debug/53/pollingLog/

Polling Log

View as plain text
This page captures the polling log that triggered this build.

Started on Feb 6, 2014 5:14:08 PM
Using strategy: Default
[poll] Last Built Revision: Revision c217dff9f833fa41043a7fe7028c5d600d1bcbfc (origin/master)
using GIT_SSH to set credentials jenkins git access
Done. Took 0.28 sec
Changes found

/job/builds.core.master.debug/52/pollingLog/

Polling Log

View as plain text
This page captures the polling log that triggered this build.

Started on Feb 6, 2014 5:13:08 PM
Using strategy: Default
[poll] Last Built Revision: Revision c217dff9f833fa41043a7fe7028c5d600d1bcbfc (origin/master)
using GIT_SSH to set credentials jenkins git access
Done. Took 0.29 sec
Changes found

when using the workaround "force polling within workspace" this works okay though.
where does it store the SHA1 that have been built when that option is not enabled (ls-remote?) ?

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/groups/opt_out.

Reply via email to