![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Vincent Latombe
|
|
Components:
|
pollscm |
|
Created:
|
07/May/13 4:15 PM
|
|
Description:
|
When a SCM poll is setup Jenkins polls a repository for changes.
When an external is referencing a specific revision (instead of head) the poll continues to check the base repository of that external for changes. If the revision of the original repository (containing the external) revision does not match the externals base head revision then it detects that there is an updated needed, this then triggers a build.
Subversion does an update but will not update the external to the revision that was detected because the external is pointing to a specific revision not the head. This then causes the poll job to continuously 'succeed' in getting updated revisions until the repositories external revision matches that of its base repositories head revision.
This is actually causing a lot of issues with Disk usage on our servers (it is a virtual server) and slowing other systems down.
|
|
Environment:
|
Windows Server 2008 R2
|
|
Project:
|
Jenkins
|
|
Labels:
|
jenkins
polling
pollscm
svn
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Giles Papworth
|
|
|
|
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.
