[p4] controlling the build line - Uri Eyal - com.perforce.perforce-user

2 messages in com.perforce.perforce-user[p4] controlling the build line

From	Sent On	Attachments
Wilf, Yaron	22 Nov 2000 14:41
Uri Eyal	27 Nov 2000 00:44

Subject:	[p4] controlling the build line
From:	Uri Eyal (ur...@AlmondNet.com)
Date:	11/27/2000 12:44:45 AM
List:	com.perforce.perforce-user

Yaron,

I used to work in a place that had such a mechanism. Perforce wasn't their tool, but you could still use this method: They implemented it by using two depots. All developers checked their work in to the first depot, but only the review people had privileges to check into the second one. The actual check in to the second depot was performed using a script that "copied" the change from one depot to the other.

This might sound complicated, but think about the alternative: If two developers submits changes #9 and #10, but change #10 gets approved before #9, than change 9 needs to be resolved again - and approved again. With a two-depots mechanism you can force the review people to accept/reject each and every change, in the order they were created. If one change takes longer to approve, this does not force the developers to wait for their changes to be approved.

-----Original Message----- hi, we need to closely monitor and control changes to the release line. We currently use the review daemon but I would like to setup a mechanism (a trigger...?) such that when a user submits a changelist the change can not be checked into the depot without approval of a review person. Ideally, when a user submits a changelist the changelist would be emailed to the designated approval person and they could permit or deny the submit via a reply to the email. any thoughts or suggestions? Has anyone implemented such a control mechanism?

thanks, -Yaron.