I use both, locking and -time. My findmerge wrappers will lock the
branches they are reading from and writing to, thereby enforcing
serializations of merges and allowing me to check whether starting a build
at a particular time is a good idea.
As soon as nobody has a lock on the branch, I am free to set the config
spec to that particular -time and be assured that I don't build from an
inconsistent base.
-- cgOn Mon, 31 Jan 2000, Murphy, Jim wrote:
> > Same here. Our build procedure creates a new view, sets the config spec for > that build view based on a template encoded into the script, and time-stamps > the config spec using the time rule. > > This effectively freezes the build view at that point in time, allowing > others to continue work. > > Of course, there is a non-zero change that you'll catch someone in the > process of checking in a series of related files, picking up some but not > all of the changes. However, that's always a risk, and I can only think of > one or two times we've hit that. > > We also have as many as 5 parallel efforts working at the same time. > Locking the vob for a couple hours at a time wouldn't be practical. > > Also, using this "one view per build" method, we archive the config spec > away for each build, allowing us to go back to that specifc version of the > source tree at some time in the future. > > Murph > > > -----Original Message----- > From: Michael Browning [mailto:mdbrowning@msn.com > Sent: Monday, January 31, 2000 12:05 PM > To: cciug@iname.com > Cc: cciug@Rational.Com > Subject: RE: [cciug] Administering Unix VOBs from NT > > > > Instead of locking the VOB we use a time stamp. > > element * /main/LATEST -time 31 Jan 08:00:00 > > Thanks > ._____._._. _ .___. > | | | | |/ /| __| > | | | < | __| /\_/\ > |_|_|_|_|_|\_\|___| (0-0) > -----------------------------too--(_)-Ooo-------------- > Service is the cornerstone, integrity the foundation, > perseverance the key, for our commitment to > excellence." Oooo. > ------------------------------.oooO---( )------------ > Michael Browning ( ) ) / > michael.browning@per-se.com \ ( (_/ > "Trust in Him" \_) > Senior Software Development Environment Engineer > Per-Se/San Bernardino 268 W. Hospitality Lane #300 > San Bernardino, Ca 92408 San Bernardino, Ca 92408 > > > > -----Original Message----- > > From: cciug@iname.com [mailto:cciug@iname.com > > Sent: Thursday, January 27, 2000 7:46 PM > > To: Browning, Michael; Niemiec, Greg; cciug > > Subject: [cciug] Administering Unix VOBs from NT > > > > > > > > > > Hello, > > Can anyone tell me, is it common practice to lock a > > vob/branch, etc before > > doing a build to ensure what > > is being built? Does anyone use other methods. > > > > Relatedly, I'm not very adept at NT and would normally > > lock a VOB from Unix (since that is where the VOB > > server is) using the vobadm account. How does one go > > about locking the Unix server VOB from NT and what > > setup is required? > > > > Thanks, jay > > (I always put my name in lowers when asking an NT > > question because I'm quite ignorant) > > > > > > --------------------------------------------------- > > Get free personalized email at http://www.iname.com > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > > > can also > > unsubscribe > > > > http://clearcase.rational.com/cciug/mailing_list.html > > > > ------ Message Header Follows ------ > > Received: from medaphis.com by corpmail.medaphis.com > > (PostalUnion/SMTP(tm) v2.2 (Build 22008) for Windows NT(tm)) > > id AA-2000Jan27.224639.1196.1629326; Thu, 27 Jan 2000 22:46:40 -0500 > > Received: from mailgw.per-se.com by medaphis.com > > (8.6.12/8.6.12) with ESMTP id > > WAA04917; Thu, 27 Jan 2000 22:45:27 -0500 > > Received: from mailgw.rational.com (mailgw.rational.com > > [130.213.254.1]) > > by mailgw.per-se.com (8.9.3+Sun/8.9.1) with ESMTP id WAA22554; > > Thu, 27 Jan 2000 22:45:26 -0500 (EST) > > Received: from mailhub.rational.com (mailhub [130.213.131.8]) > > by mailgw.rational.com (8.9.3/8.9.3/RATIONAL-mailgw) with > > ESMTP id QAA04263; > > Thu, 27 Jan 2000 16:30:32 -0800 (PST) > > Received: from localhost (daemon@localhost) > > by mailhub.rational.com (8.9.3/8.9.3/RATIONAL-mailhub) with > > SMTP id QAA12983; > > Thu, 27 Jan 2000 16:30:18 -0800 > > Received: by majordomo.rational.com (bulk_mailer v1.8); Thu, > > 27 Jan 2000 > > 16:29:47 -0800 > > Received: (from majordom@localhost) > > by mailhub.rational.com (8.9.3/8.9.3/RATIONAL-mailhub) id QAA12487 > > for cciug-outgoing; Thu, 27 Jan 2000 16:29:43 -0800 > > From: cciug@iname.com > > MIME-Version: 1.0 > > Message-Id: <000127192934LF.13500@weba2.iname.net> > > Date: Thu, 27 Jan 2000 19:29:34 -0500 (EST) > > Content-Type: Text/Plain > > Content-Transfer-Encoding: 7bit > > To: cciug@rational.com > > Subject: [cciug] Administering Unix VOBs from NT > > Sender: owner-cciug@rational.com > > X-Majordomo-Taboo: cciug > > Precedence: bulk > > > > > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > > > http://clearcase.rational.com/cciug/mailing_list.html > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > > > http://clearcase.rational.com/cciug/mailing_list.html >
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:22:42 EDT