Andrew
Andrew

Reputation: 293

ClearCase Stream Configuration for CR Based Approach

I am having trouble creating a ClearCase stream structure that is best suited for a project that works on a ticket (CR) basis. For example, if I have 7 CRs that need to be developed simultaneously , what would be the best approach?

Let's assume that I have three streams: DEV, TEST, and PROD. My 7 CRs move from DEV to TEST through the deliver operation. Of those 7 CRs, only 4 are ready for PROD. How can I move only 4 out of the 7 CRs (now grouped into one deliver) into PROD? What stream structure enables this?

I have read many (sometimes contradicting) suggestions and I have still not managed to find a solid approach.

Regards,

Andrew

Upvotes: 1

Views: 69

Answers (1)

VonC
VonC

Reputation: 1323413

Delivery only some activities and not others is quite dangerous with UCM, mainly because you have the risk to link all the activities together.

PROD
  TEST
    DEV

That will work if you deliver always from DEV to TEST, TEST to PROD (you can deliver activities then).
You could be blocked, however, by a legitimate activity file-based dependency: see "About activity dependencies in the deliver operation".

If you have any issue delivering activities, then you can use findmerge to merge only the activities you want.

See more on the "all activities are linked" and findmerge in "ClearCase : Making new baseline with old baseline activities".

Upvotes: 1

Related Questions