I would like to select the LATEST version of all elements in a directory based on the creation date otherwise select version 0. Does any one know if this can be achieved using the available config_spec syntax?
eg:
if (created_on >= 01-jan-2014)
element * /main/LATEST
else
element * /main/0
You can try a time directive of selection rule.
element /myPath/... /main/{created_since(01-Jan-2014)}
element /myPath/... /main/LATEST
That could enable you to see versions based on their creation date (see time and query)
See also "time-based rule" answer.
The second rule selection LATEST, not 0, as a way to test the first rule: remember that if a parent folder was not selected by the first rule, none of its sub-elements would be considered if it was in version 0.
Thanks for the hint VonC, I have achieved exactly what I need based on the following rules.
element -dir /myPath/... /main/LATEST
element /myPath/... /main/{created_since(01-Jan-2014)}
element /myPath/... /main/0
Related
Stumbled over this at work yesterday: I have a small VOB and created a snapshot view to access the data (source files) in it. If I give the ConfigSpec as:
load /vob/extern
element * CHECKEDOUT
element * /main/LATEST
, I will see all elements in their "LATEST" version and running a cleartool describe or xlsvtree on a single element can confirm this. Fine.
There is a src folder at the top level, having the versions "0-2", and when I setup the ConfigSpec as
load /vob/extern
element * CHECKEDOUT
element src /main/1
element * /main/LATEST
I can select the "1" version of the src directory, while keeping all other elements at "LATEST". Super.
However, this doesn't seem to work with the root folder (versions "0-7"). When I edit the ConfigSpec to
load /vob/extern
element * CHECKEDOUT
element . /main/6
element * /main/LATEST
, the version "6" of "." doesn't get selected (it's at "7"=LATEST again)! How can I accomplish this in a snapshot view?
I have also made the following, admittedly desperate, attempts
element "." /main/6
and
element "\." /main/6
, but to no avail. Searched the web/stackoverflow for quite a while and the man pages for "version_selector", "config_spec" and "wildcards_ccase" didn't offer me any explanation for the current behaviour.
I also tried another
rm -rf *
cleartool update
after setting the ConfigSpec, but the version of "." stays at "7".
The relative path '.' does not seem to work, and the config spec falls back to the next valid rule.
Try and use, after reading config_spec Pattern, an absolute path:
element /vob/extern /main/6
# or
element /vob/extern/ /main/6
I want the LATEST archived elements everywhere except in folder /view/my_view/vobs/the_vob/xxx/yyy/ where I want elements tagged LBL_01. The config spec below doesn't work.
element /the_vob/xxx/yyy/... LBL_01
element * CHECKEDOUT
element * /main/LATEST
You cannot apply the rule directly to /the_vob/xxx/yyy/
You need first to select the parent folder versions:
/the_vob
/the_vob/xxx
So:
element * CHECKEDOUT
element /thevob /main/LATEST
element /thevob/xxx /main/LATEST
element /the_vob/xxx/yyy/... LBL_01
element * /main/LATEST
The order is important: first select the parent folders, then apply your special rules.
If this is on Unix, the VOB tag to use would be /vobs/the_vob and not /the_vob. The path in the element line needs to be the VOB tag as shown by lsvob on the view server.
I am guessing that by "doesn't work" you mean a cleartool ls shows that you're seeing /main/LATEST as the rule.
I have tiny question about ClearCase. Help me please! When does config spec start to work? When I click CHECK OUT or CHECK IN ? I have test.c and I have config spec
element * CHECKEDOUT
element * .../branch_1/LATEST
element * /main/LATEST -mkbranch branch_1
then I modify test.c, then I change config spec:
element * CHECKEDOUT
element * .../branch_2/LATEST
element * /main/LATEST -mkbranch branch_2
Then I Check in test.c and I have: created /main/branch_1/1. BUT WHY???
The config spec will apply the rules on each update and on checkout, and on checkin (but not as you think it would).
On checkin, the new version will be created in the branch it has been checked out (here branch_1).
That new version might not be selected by the new config spec, BUT the branch in which it has been checked out is NOT changed by said new config spec.
Changing branch1 in branch2 while test.c is already checked out (in branch1) doesn't change anything. It will be checked in in branch_1.
Now that you will create a version on branch1 on checkin for test.c (even with your second config spec), you need to realize that all future checkout/checkins will take place on that same branch for test.c, because:
the rule element * branch_1/LATEST will keep the new versions on that branch
the rule element * /main/LATEST -mkbranch branch_2 is only valid for version checked out from main (and test.c is no longer on /main, it is on branch1: /main/branch1)
This config spec would make sure that all new versions (after the first checkin of test.c on branch1) are done on branch2:
element * CHECKEDOUT
element * .../branch_2/LATEST
element * ../branch_1/LATEST -mkbranch branch_2
element * /main/LATEST -mkbranch branch_2
The order of the rules is important, because the first one that can be applied "wins" (i.e. the pothers are ignored).
See this concrete example of config spec in "Config Spec to display labeled files from 2 branches".
Note that after the first checkin of test.c, you will get a new version created on branch1, as explained before.
Yet your second config spec will select /main/1, not /main/branch1/1.
That is because of an incorrect rule in your second config spec:
element * branch_1/LATEST
This one would select the right version:
element * .../branch_1/LATEST
But if your second config spec has no rule regarding branch1, test.c will still be selected as /main/1: there is no version created on branch2, so element * /main/LATEST is the only rule that can be applied.
I am workng with base ClearCase. Please consider my config spec:
element * CHECKEDOUT
element /cl5_sw_ste/DCT/*/... /main/rel_drop5/int_drop5/cl5_p65719_AUTE/LATEST
element /cl5_sw_ste/DCT/*/... /main/rel_drop5/int_drop5/LATEST -mkbranch cl5_p65719_AUTE
element /cl5_sw_ste/DCT/*/... /main/rel_drop5/LATEST -mkbranch int_drop5
element /cl5_sw_ste/DCT/*/... /main/0 -mkbranch rel_drop5
INTENT: Any checkout of existing elements automatically occurs on branch /main/rel_drop5/int_drop5/cl5_p65719_AUTE and that this branching scheme is used automatically for the creation of any new elements (of which I presently have none).
When I navigate to the root of VOB cl5_sw_ste in ClearCase Explorer, select New--> Folder from the right pane's context menu, and try to create my first element---directory element DCT---, I receive the following error:
The system cannot find the file specified.
Why is this occurring?
Thanks,
Dave
Those selection rules are for elements inside DCT, not for DCT itself.
When you are adding DCT, it creates a version in /main/0.
And none of your rules selects /main/0.
you should add least add one selection rule at the end:
element * /main/LATEST
That is called a "config stop-rule", as illustrated in "ClearCase Branching using configspec".
I have very little knowledge about ClearCase and would like to learn more.
I have created a branch BR_PHASE2 under /main.
I have used the following command to checkout the files into the branch:
element * CHECKEDOUT
element * .../BR_PHASE2/LATEST
element * /main/LBL_MS_PHASE2_04-NOV-2010 -mkbranch BR_PHASE2
The problem now is how do I access files from the branch ??
I am not able to even open the VOB if I switch to this config spec:
element * CHECKEDOUT
element * /main/BR_PHASE2/LATEST
Am I writing the config spec wrong ?? The error i am getting when I try to set the config spec as above:
Warning: New config spec makes current working dir invisible.
What are the steps to actually access the branch that I have created ??
The problem is:
What directories actually have:
a version in the branch BR_PHASE2 ?
a version labeled LBL_MS_PHASE2_04-NOV-2010 ?
If you only branch/labeled all files under /myVob/myDirectory, then the directory /myVob itself won't never be branched/labeled.
That means the following config spec won't be able to select any version for /myVob, making all the other rules for any file under /myVob useless:
Until ClearCase is able to select at leat one valid version of /myVob, it won't be able to select any version for any file under /myVob.
element * CHECKEDOUT
element * /main/BR_PHASE2/LATEST
You should always end your config spec with a "config stop-rule" like:
element * /main/LATEST
or at least:
element /myVob /main/LATEST
Add one of those at the end of your config spec, and the view should work as expected.
The ClearCase config spec mechanism is a composition-based one: to know more about it, see the SO answer "Flexible vs static branching (GIT vs Clearcase/Accurev)".
The OP adds:
You have mentioned to always end the cs with: element * /main/LATEST,
Not necessarily:
If you want to be sure to only view the files under /myVob/myDir with the right branch/label, you could use as I mentioned above:
element /myVob /main/LATEST
The rule applies only to /myVob (not to anything under /myVob).
That allows ClearCase to get past /myVob (because it can at least select a valid version for it) and start applying the other selection rules to the sub-directories.
but if I want to check out the files only from the branch BR_PHASE2, wont this create an error. I am saying that when I end it with /main/LATEST and checkout and check in files , it is updated in main branch. what do I do about it ?
It depends on the config spec you are using:
element * CHECKEDOUT
element * /main/BR_PHASE2/LATEST
element * /main/LATEST
would indeed create new version in the main branch
element * CHECKEDOUT
element * .../BR_PHASE2/LATEST
element * /main/LBL_MS_PHASE2_04-NOV-2010 -mkbranch BR_PHASE2
element * /main/LATEST
would not, because the third rule would apply first, if the element has been labeled LBL_MS_PHASE2_04-NOV-2010.
Your first config spec seems to be ok. It sais that all the files you try to change from the label 'LBL_MS_PHASE2_04-NOV-2010' will be branched to BR_PHASE2. Just try to checkout something, and watch the version tree.
Also, the second config spec tells to see all the files, that belong ONLY to the branch, but if you haven't checkout to branch any, then you will see nothing.
Try the following:
element * CHECKEDOUT
element * /main/LBL_MS_PHASE2_04-NOV-2010
element * /main/BR_PHASE2/LATEST
so that you have the directory structure by selecting the label and your files from branch.