ClearCase Config Spec ignored?

Good morning,

I have a quick Q: I've a CC Snapshot view configured for a TeamCity project which has the following config spec:

element * CHECKEDOUT element * iRMA_V3.0_SP3_CF element * /main/LATEST load \PM_CT\DevelopmentPhase\Implementation\Resources load \PM_CT\DevelopmentPhase\Implementation\Applications\DiffMerge load \PM_CT\DevelopmentPhase\Implementation\Applications\Cali-MERO_2.0


Now when using that view and having a look at a file from e.g. the 'version tree', I do see that the view itself is working perfectly fine and is 'focused' on the iRMA_V3.0_SP3_CF labeled files, e.g.:

view.gif

However, TeamCity includes change #9, which comes after that label etc in the build? Why's that? Does TeamCity modify or overwrite the config spec's settings?

Br,
-Jörg Battermann

3 comments
Comment actions Permalink

Yes. And it seems correct.

I think that Config Spec does matter with ClearCase, and not with ClearCase plugin for TeamCity.

Regards,

Olivier.

0
Comment actions Permalink

Oliver,

you mean it's correct that the TeamCity plugin ignores the corresponding config spec setting? How would I configure my view properly then so TeamCity does respect the wanted versions?

-J

0
Comment actions Permalink

Please note that I'm a newbie on TeamCity with ClearCase.

you mean it's correct that the TeamCity plugin ignores the corresponding config spec setting?

I mean that TeamCity doesn't matter ClearCase config spec settings, as it only ask ClearCase client (cleartool) to do the job with existing ClearCase snapshot view settings.

How would I configure my view properly then so TeamCity does respect the wanted versions?


I don't know. You may need a ClearCase expert.

Regards,

Olivier.

0

Please sign in to leave a comment.