2
votes

I am using jenkins to build my project. My source code is in clearcase. I want to get the latest code from latest local code and make a build. All the setup worked

ClearCase repository Structure - 2 projects.

Main_Projects
-Project_1
--Project_1_Ver1
---Project_1_Ver1_TST
----Project_1_Ver1_LCL
--Project_1_Ver2
---Project_1_Ver2_TST
----Project_1_Ver2_LCL

-ProjectTwo
--Project_2_Ver1
---Project_2_Ver1_TST
----Project_2_Ver1_LCL

JENKINS Project - Source Management
Base ClearCase
view tag: Jenkins_Project_1_Ver1_LCL
view path: Jenkins_Project_1_Ver1_LCL

This is working config spec element * CHECKEDOUT
element * .../Project_1_Ver1_LCL/LATEST
element * .../Project_2_Ver1_LCL/LATEST
element * /main/LATEST

Load Rules
\Proj1
\proj2

I had to point to new version for one project and I updated the config spec as follows

view tag: Jenkins_Project_1_Ver2_LCL
view path: Jenkins_Project_1_Ver2_LCL

element * CHECKEDOUT
element * .../Project_1_Ver2_LCL/LATEST
element * .../Project_2_Ver1_LCL/LATEST
element * /main/LATEST

Load Rules
\Proj1
\proj2

After this change, jenkins clearcase plugin does not get the code for the Project_1_Ver2_LCL stream any more.

1

1 Answers

0
votes

In case you have a parent folder labelled with V1 only and not V2 (which would make all V2 sub-elements inaccessible), add a V1 rule (after the V2 one)

element * .../Project_1_Ver2_LCL/LATEST
element * .../Project_1_Ver1_LCL/LATEST

Another approach would be to make sure the baseline V2 is a full one, not an incremental one. That way, its associated label would be present on all the elements of the component.