Search code examples
clearcasecleartool

Clearcase configspec for view based on composite baseline

i am working on some scripts to migrate to git. I want to make a view based on a composite baseline to commit that data. I have several baselines to 'checkout' Normal baselines I do with:

element * CHECKEDOUT
element * baseline -nocheckout
element * /main/0 -ucm -nocheckout 

load /vobs/[component1]
load /vobs/[component2]
load /vobs/[component3]

But when the baseline is a composite the view stays empty...

What can I do?

Regards,

jr00n

Solution

  • I confirm that a composite baseline is a metalabel: when used in a base ClearCase view, it doesn't select any files, since its role is to group normal baselines.

    If you can use an UCM view (based on a dedicated UCM project), that would be easier because:

    • your composite baseline would select the right file (in that it would build the right config spec with all the grouped baselines in it)
    • your normal baselines would select the right files (which is not always the case in a normal base ClearCase view, when the baseline isn't a full one, but an incremental one)

    So my advice: use a (dynamic) UCM view based on an Integration stream, where you can rebase UCM baselines at will.