Shawn M. Jones created JENKINS-12670:
----------------------------------------
Summary: "Double Build" Polling Issue with Subversion Plugin
Key: JENKINS-12670
URL: https://issues.jenkins-ci.org/browse/JENKINS-12670
Project: Jenkins
Issue Type: Bug
Components: subversion
Affects Versions: current
Environment: Red Hat Enterprise Linux 6.1 running Jenkins 1.449 from
RPM (within Winstone).
Reporter: Shawn M. Jones
We are using the SVN polling option for Jenkins. It is set to poll the SVN
repository once a minute.
The polling log states:
Started on Feb 7, 2012 11:07:02 AM
Received SCM poll call on for n-oa on Feb 7, 2012 11:07:02 AM
https://XXXXXX is at revision 19,322
(changed from 19,321)
Done. Took 0.25 sec
Changes found
Under "Changes" on the page for the given build, there is the following:
Revision: 19321
No changes.
But then the job never performs the SVN update on the workspace, building from
the old codebase. The next poll detects the change, updates the workspace, and
builds again. This produces 2 builds for some commits.
We have not been able to determine what triggers the "double build", because,
though it is happening often, it doesn't happen every time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
