-
Improvement
-
Resolution: Unresolved
-
Major
-
None
We recently upgraded to ClearCase plugin 1.2.1 from a version which is about a year old (sorry not sure the version). The change to lshistory from the whole VOB since the last build means that for large VOBs with a small amount of elements which are interesting to the build this polling activity can take a very long time especially if the job has infrequent changes.
Would it be possible to have an option to use the lshistory -r functionality as it used to be, or alternatively to only poll for changes since the last time it was polled?
[JENKINS-7481] ClearCase polling change degrades performance for large VOBs
bhalter
created issue -
anb0s
added a comment - Integrated patch at https://github.com/anb0s/clearcase-plugin/tree/integrate_1.3.8
anb0s
added a comment - Integrated patch at https://github.com/anb0s/clearcase-plugin/tree/integrate_1.3.8 Code changed in jenkins
User: unknown
Path:
src/main/java/hudson/plugins/clearcase/ClearCaseUcmSCM.java
src/main/java/hudson/plugins/clearcase/ClearTool.java
src/main/java/hudson/plugins/clearcase/ClearToolExec.java
src/main/java/hudson/plugins/clearcase/base/BaseHistoryAction.java
src/main/java/hudson/plugins/clearcase/history/AbstractHistoryAction.java
src/main/java/hudson/plugins/clearcase/ucm/UcmChangeLogAction.java
src/main/java/hudson/plugins/clearcase/ucm/UcmHistoryAction.java
src/test/java/hudson/plugins/clearcase/ClearCaseSCMDummy.java
src/test/java/hudson/plugins/clearcase/ClearCaseSCMTest.java
src/test/java/hudson/plugins/clearcase/ClearCaseUcmSCMDummy.java
src/test/java/hudson/plugins/clearcase/ClearCaseUcmSCMTest.java
src/test/java/hudson/plugins/clearcase/ClearToolExecTest.java
src/test/java/hudson/plugins/clearcase/base/BaseHistoryActionTest.java
src/test/java/hudson/plugins/clearcase/ucm/UcmChangeLogActionTest.java
src/test/java/hudson/plugins/clearcase/ucm/UcmHistoryActionTest.java
http://jenkins-ci.org/commit/clearcase-plugin/f905ea64158c1606184b445c4e7a64d4851fc37e
Log:
http://issues.jenkins-ci.org/browse/JENKINS-7481
added internal flag for using -recurse
anb0s
made changes -
| Fix Version/s | New: current [ 10162 ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
bbonn
added a comment - Hi,
Just upgraded to 1.3.11, thinking I would see lshistory -r instead of -all in the console log. But I haven't seen a difference. I have tested on some builds that have not built in a while hoping the lshistory portion would be shortened, but no-go. Am I missing some config, or did I misread this bug? I appreciate any guidance. Thanks!
bbonn
added a comment - Hi,
Just upgraded to 1.3.11, thinking I would see lshistory -r instead of -all in the console log. But I haven't seen a difference. I have tested on some builds that have not built in a while hoping the lshistory portion would be shortened, but no-go. Am I missing some config, or did I misread this bug? I appreciate any guidance. Thanks! anb0s
added a comment - Hi,
i've just checked the sources - it looks like only part of my patch was included in my pull request. I see the whole changes only in my private branch for 1.3.9. I've reopened the issue and will create another pull request. Sorry, i'm new to git, something went wrong...
anb0s
added a comment - Hi,
i've just checked the sources - it looks like only part of my patch was included in my pull request. I see the whole changes only in my private branch for 1.3.9. I've reopened the issue and will create another pull request. Sorry, i'm new to git, something went wrong... anb0s
made changes -
| Assignee | Original: Vincent Latombe [ vlatombe ] | New: anb0s [ anb0s ] |
| Resolution | Original: Fixed [ 1 ] | |
| Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
bbonn
added a comment - Sounds good. Any idea when they will do another pull? In the meantime do you have a version I could test with from your branch? I was wondering if there was any new config we have to do to force the -r in stead of -all. Thanks again!
bbonn
added a comment - Sounds good. Any idea when they will do another pull? In the meantime do you have a version I could test with from your branch? I was wondering if there was any new config we have to do to force the -r in stead of -all. Thanks again! 
I just created request for using other load rules fields to select folders and/or files instead of VOBs: http://issues.jenkins-ci.org/browse/JENKINS-8949
For this use case lshistory -recurse is faster then -all. We should add new option for experts:
use lshistory -all (optimized for whole VOBs)
( ) use lshistory -recurse (optimized for small amount of folders and files)