CODEWITHSUNDEEP
clearcaseclearcase-ucm
Samselvaprabu
Samselvaprabu

Reputation: 18147

Why dependency is triggered even if an activity is made as an obsolete?

In UCM project we are trying to deliver activity to default stream.

It is displaying that activity is having dependency with another activity.

As the dependent activity has no useful info we obsoleted it. But still it doesn't allow us to proceed and it force us to deliver that ?

Why dependency is being triggered even if the activity is obsolete?

Upvotes: 2

Views: 647

Answers (2)

Pulak Agrawal
Pulak Agrawal

Reputation: 2481

@Samselvaprabu I have seen this happen before, this smells of hyperlinks. Can not be 100% sure if your problem is exactly same, but they have worked for me in the past:

    • checkvob -ucm activity:@\PVOB which might point you to a bad hyperlink

    • checkvob -fix

  2. Use ucmutil to do a similar job

Please be careful, there are always risks associated with messing with hyperlinks, so read the manuals and/or technotes before you actually run a checkvob -fix or something intrusive.

Upvotes: 2

VonC
VonC

Reputation: 1323553

The activity will be associated with your deliver (without choice) if:

  • there is a common file with other activities (file dependency)
  • you previously did a deliver to another stream (in which case it automatically link all the remaining activities together)

If the activity is small enough, the best course of action remains to deliver everything, and to cancel what you don't need.

If there is really no common file, one option mentioned in this old 2003 thread would be to try and change the owner (only by a ClearCase admin) of the activity.
See cleartool project:

cleartool protect -chown aNewOwner activity:anActivity@\aPvob

(you might have to "cleartool unlock activity:anActivity@\aPvob" first if it was "lock -obsolete")

Upvotes: 2

Related Questions