2 messages in com.perforce.perforce-user[p4] Jobs, Integrating and Disintegra...
FromSent OnAttachments
Howe, Peter21 Dec 2000 02:32 
Richard Brooksby21 Dec 2000 04:45 
Subject:[p4] Jobs, Integrating and Disintegrating
From:Howe, Peter (Pete@primark.com)
Date:12/21/2000 02:32:57 AM
List:com.perforce.perforce-user

I'm considering using Perforce on a project containing roughly 6500 source files.

We have our own problem tracking software which, it seems, we could tie in with Perforce's jobs.

In our environment, all source changes are attributed to one "job". (But, because of the way we work - given that some jobs might involve a lot of work - there might be many p4 submit's per job; thus several changelists per job.)

Changes done as part of a job may be merged (integrated) to different branches off the main line (this should be atomic) - all changes should be integrated, or none. Likewise, it is possible that, if a change fails testing, or if it is decided for commercial reasons that a change should not go into a release, the job's changes might be "disintegrated" from a branch.

So... two questions:

1. How do we go about this "disintegration" (especially if the job's changes are not the head changes on a file?) 2. Is there anyway of *forcing* every changelist to be associated with a job?

Many thanks in advance, Pete

----------------------------- Peter Howe, Thomson Financial Portfolio Solutions Group W: +44 (020) 7324 9701 X: 1701 F: +44 (020) 7729 8439 H: +44 (020) 7690 4158 M: +44 (07771) 992 331 E: peter.howe at primark.com http://www.tf-portfoliosolutions.net or peterhowe at xenzero.com http://www.xenzero.com