From owner-freebsd-chat Fri Apr 12 9:14: 7 2002 Delivered-To: freebsd-chat@freebsd.org Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87]) by hub.freebsd.org (Postfix) with ESMTP id 32A5837B405 for ; Fri, 12 Apr 2002 09:14:03 -0700 (PDT) Received: from attbi.com ([12.237.241.112]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020412161357.SMVK15826.rwcrmhc54.attbi.com@attbi.com>; Fri, 12 Apr 2002 16:13:57 +0000 Message-ID: <3CB707CF.D6DEAA19@attbi.com> Date: Fri, 12 Apr 2002 11:14:08 -0500 From: Joe Halpin X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686) X-Accept-Language: en MIME-Version: 1.0 To: Terry Lambert Cc: dan@langille.org, chat@freebsd.org Subject: Re: setting up daily builds References: <20020411214456.0E68B3F2D@bast.unixathome.org> <3CB63991.7B33851F@mindspring.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Terry Lambert wrote: > > Dan Langille wrote: > > What do you folks do if you want to build a system/application on a daily > > basis? How do you view the results? Any history on those results > > (yesterday's build, last Tuesday's build, etc)? > > Normally, I do not set up daily builds for FreeBSD, because of > the way the tree consistency is not guaranteed on CVSup snapshots, > and the lack of enforcement against committers of buildability on > all commits. > > For a normal corporate production environment, I generally > maintain two checked out tree instances, and update and > build via cron jobs. Each checkout is done by (1) tagging the > tree and then (2) checking out via the tag. > > With two instances, it's possible to maintain a rolling build > that will automatically roll back changes which break a build > under the tag, and inform the guilty party of the files involved > in the breakage (you do it this way so that your tags can be > light-weight instead of being full on branch tags). How do you go about identifying the guilty parties? For example, if a subsystem that other code depends on breaks, that would probably cause failures in dependent subsystems. Would the owners of the dependent subsystems get email as well in that case? Also, if a subsystem fails because of an error in a header file exported by some other subsystem (which didn't fail to build), will the right developer get the email? I'm very interested in how you deal with things like this. Thanks Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message