Jenkins Clearcase Plugin Not detecting changes and triggering continually on erroneous-ConfigSpec change detection

[Phil Lord]

Hi,

I'm experiencing two issues using the Jenkins ClearCase plugin. It does not detect changes in the VOB and it continually triggers a build when the config spec specified in Jenkins does not match the config spec defined for the current View in ClearCase. See details below. Thanks in advance for your help!!
Phil

Jenkins 1.5.10
Jenkins-Clearcase Plugin 1.5
Windows 7

When Config spec field under Project->Configure->Soucre Code Managermen matches the config spec of the View Tag, the SCM Poll does not trigger a build, but when config spec of the View Tag does not match the Jenkins Project's config spec, a build is triggered each time the poll runs. See Base ClearCase Polling Logs below.

The other issue is that changes to the ClearCase VOB are not being detected and/or build not triggered. If I enter the command found in the log (below), at the cleartool command line, it shows the files that were modified.

lshistory -all -since 19-may-14.00:21:25utc+0000 -fmt '\"%Nd\" \"%u\" \"%En\" \"%Vn\" \"%e\" \"%o\" \n%c\n' -branch brtype:dev3.0 -nco M:\plord_HnwTester_working_

view\wint_hat\Source\Test_Automation\HNW_Tester_EclipseWorkspace\HNWTester\src\com\harris\hnw\tester




When CONFIG SPECS DON"T MATCH
-----------------------------
Base ClearCase Polling Log

Started on May 18, 2014 8:06:24 PM
Checking if build is running
Checking if a build has already happened
Checking if revision state is known
Checking if we have a build with a valid workspace
*************************** get view CSPEC ***********************
[tester] $ cleartool catcs -tag plord_HnwTester_working_view
element * CHECKEDOUT

# ----- LABEL ------------
#element * HNW_3.0_00.04.06
#element * HNW_3.0_00.06.09

# -----AI BRANCH ------------
#element * .../dev3.0/ai0603/LATEST
#element * /main/dev3.0/LATEST -mkbranch ai0603

# -----PTR BRANCH ------------
#element * .../dev3.0/ptr0677/LATEST
#element * /main/dev3.0/LATEST -mkbranch ptr0677

# ----- DEV BRANCH ------------
element * .../dev3.0/LATEST
element * /main/LATEST -mkbranch dev3.0

#----- MAIN LATEST --------------
element default_config_spec /main/LATEST
element *.doc /main/LATEST
element *.ppt /main/LATEST
element *.xls /main/LATEST
element *.mdb /main/LATEST
element *.pdf /main/LATEST
element *.mdl /main/LATEST
element *.ptl /main/LATEST
element *.cat /main/LATEST
element *.vsd /main/LATEST
element *.docx /main/LATEST
element *.pptx /main/LATEST
element *.xlsx /main/LATEST
element "/wint-ng/HNW/Bin/..." /main/LATEST
element "/wint-ng/HNW/CFE/..." /main/LATEST
element "/wint-ng/HNW/COTS/..." /main/LATEST
element "/wint-ng/HNW/Tools/..." /main/LATEST
element "/wint-ng/Test/..." /main/LATEST
element "Documents/..." /main/LATEST

******************************************************************
[WARNING] CSPEC configured != catcs (view)
REASON: New config spec detected.
Done. Took 0.28 sec
Changes found

When CONFIG SPECS DO MATCH
-----------------------------
Base ClearCase Polling Log

Started on May 18, 2014 8:26:24 PM
Checking if build is running
Checking if a build has already happened
Checking if revision state is known
Checking if we have a build with a valid workspace
*************************** get view CSPEC ***********************
[tester] $ cleartool catcs -tag plord_HnwTester_working_view
element * CHECKEDOUT

# ----- LABEL ------------
#element * HNW_3.0_00.04.06
#element * HNW_3.0_00.06.09

# -----AI BRANCH ------------
#element * .../dev3.0/ai0603/LATEST
#element * /main/dev3.0/LATEST -mkbranch ai0603

# -----PTR BRANCH ------------
#element * .../dev3.0/ptr0677/LATEST
#element * /main/dev3.0/LATEST -mkbranch ptr0677

# ----- DEV BRANCH ------------
element * .../dev3.0/LATEST
element * /main/LATEST -mkbranch dev3.0

#----- MAIN LATEST --------------
element default_config_spec /main/LATEST
element *.doc /main/LATEST
element *.ppt /main/LATEST
element *.xls /main/LATEST
element *.mdb /main/LATEST
element *.pdf /main/LATEST
element *.mdl /main/LATEST
element *.ptl /main/LATEST
element *.cat /main/LATEST
element *.vsd /main/LATEST
element *.docx /main/LATEST
element *.pptx /main/LATEST
element *.xlsx /main/LATEST
element "/wint-ng/HNW/Bin/..." /main/LATEST
element "/wint-ng/HNW/CFE/..." /main/LATEST
element "/wint-ng/HNW/COTS/..." /main/LATEST
element "/wint-ng/HNW/Tools/..." /main/LATEST
element "/wint-ng/Test/..." /main/LATEST
element "Documents/..." /main/LATEST

******************************************************************
Checking view validity
[tester] $ cleartool lsview plord_HnwTester_working_view
* plord_HnwTester_working_view \\pbympnas1\wc_ccs05_view1\WINT_NG\HARRIS\plord\plord_HnwTester_working_view.vws

[tester] $ cleartool startview plord_HnwTester_working_view

Checking if there are changes in history
[tester] $ cleartool lsview plord_HnwTester_working_view
* plord_HnwTester_working_view \\pbympnas1\wc_ccs05_view1\WINT_NG\HARRIS\plord\plord_HnwTester_working_view.vws

[tester] $ cleartool startview plord_HnwTester_working_view

[m_] $ cleartool lshistory -all -since 19-may-14.00:21:25utc+0000 -fmt '\"%Nd\" \"%u\" \"%En\" \"%Vn\" \"%e\" \"%o\" \n%c\n' -branch brtype:dev3.0 -nco M:\plord_HnwTester_working_view\wint_hat\Source\Test_Automation\HNW_Tester_EclipseWorkspace\HNWTester\src\com\harris\hnw\tester
Done. Took 2 sec
No changes

[Vincent Latombe]

Hi Phil,

when working with dynamic views, view path should be equal to the view tag.

So instead of using m_, you should specify the same value as the view tag you specified above.

Let me know if it works for you.

Cheers,

Vincent

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Phil Lord]

Ok, I'll give it a try. Thanks Vincent!
Phil

[wak...@comcast.net]

I have an android build that runs junit tests. I can use ANT and run the test from the command line without issue.

It takes about 10 minutes to complete. It is reliable.

When I run it within Jenkins, it seems to "hang" in random tests (I look in the log being generated and see it seemly spinning

its wheels in different tests). It can run for hours and not complete. I am using the same version of ANT and Java in Jenkins

as I am using from the command line.

These tests are using a LOT of memory. Again, they run fine outside of Jenkins. Any idea of how to troubleshoot what

Jenkins is waiting on ?? Could there be a memory issue ?? (I would think that Jenkins is launching ANT in a separate process

so it should be no different (from a memory perspective) than me running from the command line).

thanks

walter

[Phil Lord]

Vincent,

Setting the view path per your suggestion improved things! Now the lshistory command displays the changes that occurred (as shown below), but the plugin reports "No changes"
Phil

Checking if there are changes in history
[tester] $ cleartool lsview plord_HnwTester_working_view
* plord_HnwTester_working_view \\pbympnas1\wc_ccs05_view1\WINT_NG\HARRIS\plord\plord_HnwTester_working_view.vws

[tester] $ cleartool startview plord_HnwTester_working_view

[plord_HnwTester_working_view] $ cleartool lshistory -all -since 20-may-14.18:18:22utc+0000 -fmt '\"%Nd\" \"%u\" \"%En\" \"%Vn\" \"%e\" \"%o\" \n%c\n' -branch brtype:dev3.0 -nco M:\plord_HnwTester_working_view\wint_hat\Source\Test_Automation\HNW_Tester_EclipseWorkspace\HNWTester\src\com\harris\hnw\tester
"20140520.142136" "lstarr01" "M:\plord_HnwTester_working_view\wint_hat\Source\Test_Automation\HNW_Tester_EclipseWorkspace\HNWTester\src\com\harris\hnw\tester\testprocedures\build10\TestCase_Build_10_4.java" "\main\dev3.0\38" "create version" "checkin" 
configureForCstStart now writes the CST configuration XML

"20140520.142121" "lstarr01" "M:\plord_HnwTester_working_view\wint_hat\Source\Test_Automation\HNW_Tester_EclipseWorkspace\HNWTester\src\com\harris\hnw\tester\TestCase.java" "\main\dev3.0\287" "create version" "checkin" 
configureForCstStart now writes the CST configuration XML


Done. Took 2.4 sec
No changes

On Tuesday, May 20, 2014 8:24:43 AM UTC-4, Phil Lord wrote:

[Vincent Latombe]

Hi Phil,

Your load rule is incorrect. Indeed it should be relative to the view path, so start with the job name

--

[Vincent Latombe]

I meant vob name (stupid phone)

[Phil Lord]

Vincent,

You the man! It's working! I championed Jenkins and was getting a lot of unwanted viability due to it not working, but now they'll focus on the next fire.

Thanks again Vincent!
Ciao!
Phil

[Amit Dar]

Hi,

I read this thread several times, and still no results.

I see the changes are detected, but the plugin reports "No changes" at the end.

are you guys still alive? :)