Details
-
New Feature
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
Our projects are generally configured to poll every 5 minutes for changes. A number of these projects use the main branch for development within the same vob. We now can get into the situation where the polling (or generating a change set) can take a really long time if the project to be polled has not had any changes in a while but other projects using the same branch (typically main) have made a lot of changes.
Could the polling be changed to only look for changes since the last poll, not the last build? Otherwise the change history that comes back includes potentially 1000's of changes from other projects. Any other solution that addresses this would be great!
Attachments
Issue Links
- depends on
-
-
- Closed
-
Activity
schmid03
added a comment - We have the same problems due to main branch development in some projects in our vob. So we have the same problem and additional very long polling times. We poll every 5 min. for continuous integration, but if many changes are inside the vob since last build it takes about 20 mins. to more than one hour. See also http://issues.jenkins-ci.org/browse/JENKINS-5394.
schmid03
added a comment - We have the same problems due to main branch development in some projects in our vob. So we have the same problem and additional very long polling times. We poll every 5 min. for continuous integration, but if many changes are inside the vob since last build it takes about 20 mins. to more than one hour. See also http://issues.jenkins-ci.org/browse/JENKINS-5394 . The new polling logic enables to store the last polling time.
Change is in trunk, you're welcome to test.
schmid03
added a comment - Many thanks, I will check it a.s.a.p. This week I can't do the check, since our Clearcase Servers are maintained and we can't do any changes to our sources 
schmid03
added a comment - Many thanks, I will check it a.s.a.p. This week I can't do the check, since our Clearcase Servers are maintained and we can't do any changes to our sources Currently I'm trying to check the implementation. I've built a new clearcase plug-in from svn trunk. The plug-in is installed and now I'm searching for the option to activate the behavior. Is there such a config or is this feature always active?
BR,
Alfred
schmid03
added a comment - - edited Currently I'm trying to check the implementation. I've built a new clearcase plug-in from svn trunk. The plug-in is installed and now I'm searching for the option to activate the behavior. Is there such a config or is this feature always active?
BR,
Alfred schmid03
added a comment - I've tested this implementation with hudson on linux (RHEL 5, java 1.6 update 20) with 14 active projects. I haven't found any issues until know.
schmid03
added a comment - I've tested this implementation with hudson on linux (RHEL 5, java 1.6 update 20) with 14 active projects. I haven't found any issues until know. 
Hrm. The problem is that the polling time isn't actually recorded anywhere we can get at it - Hudson doesn't record polling anywhere but printing it out to the log. I'm not sure whether that'd be something it'd make sense to store somewhere - and if so, I'm not sure where. I'm going to change this to a feature request and bump the priority down a bit, since it'd require at the very least some major changes to the plugin.