7 messages in com.perforce.perforce-user[p4] possible to check in a file at a...| From | Sent On | Attachments |
|---|---|---|
| Chris Mitchell | 01 Aug 2003 11:41 | |
| Robert Duff | 01 Aug 2003 11:47 | |
| Chris Mitchell | 01 Aug 2003 12:02 | |
| Noel Yap | 01 Aug 2003 12:25 | |
| Blake Ramsdell | 01 Aug 2003 12:27 | |
| Robert Duff | 01 Aug 2003 12:41 | |
| Mike Castle | 02 Aug 2003 13:08 |
| Subject: | [p4] possible to check in a file at an arbitrary rev |
|---|---|
| From: | Blake Ramsdell (bla...@brutesquadlabs.com) |
| Date: | 08/01/2003 12:27:54 PM |
| List: | com.perforce.perforce-user |
-----Original Message----- From: perforce-user-admin at perforce.com [mailto:perforce-user-admin at perforce.com] On Behalf Of Chris Mitchell Sent: Friday, August 01, 2003 12:03 PM To: Robert Duff; perforce-user at perforce.com Subject: RE: [p4] possible to check in a file at an arbitrary rev
It's been our tradition to name builds according to the rev of the Makefile. (We create a new rev for each build.) Since we're carrying over from our old system, if I used the current rev in P4 we'd have a problem since that name has in fact been used already. We don't want to rock the boat too much and go to a different naming scheme. (I tack on a "1." to the p4 rev to keep it looking the same.) So I'd like to up the rev of the makefile in p4 to the last one we used in our old system +1.
Personally, I'd do my best to get everyone to abandon this approach, and use the last submitted changelist number for the build ID. Yes, it will be sad for a short period, and the build IDs won't be monotonically incrementing, but they will be unique, and higher numbers will be more recent builds, and that's what's important. Plus you'll be able to recreate the environment for that build by simply syncing to that changelist (as opposed to figuring out which changelist the makefile was submitted).
Also, if you reorganize the source tree and the makefile moves to a new location, his revision number will start back at "1" again.
We use a combination of the date + changelist here. For instance, last night we built 20030801-2890. The date is just so everyone feels better -- the only thing I care about is the "2890" which is the last submitted changelist for the build.
The boat's already been rocked by switching to Perforce -- make the most of it ;).
Blake