From: Taylor, K. <Kev...@pa...> - 2003-04-11 14:48:51
|
How can we make sure, that everything is build in the correct order. It seems to be possible to do this via a certain time, a build starts, but this is not as good, as we would like to have it, because we can not guarantee, that componente 1 takes 5 minutes to compile and not say 10 minutes. One method, if the CC's have access to a common file system: When the first build finishes sucessfully, it creates a temp file with a status code. The next job wakes every 5 minutes and looks for this file. If it finds the file, it looks for a successful status code. It then deletes the temp file and runs and if it is sucessful it creates a differently named temp file with it's status code. The third job is also waking every 5 minutes and looking for job number 2's temp file, etc, etc. With this method there is some flexibility. For instance, you have 2 builds that create jars and a third build that uses those 2 jars. You can run the first 2 builds concurrently and the third build doesn't start until it sees that both "jar" builds have completed successfully (by reading in and then deleting the first 2 build's temp files). --Kevin Taylor Sr Web Developer > -----Original Message----- > From: mm...@gm... [SMTP:mm...@gm...] > Sent: Friday, April 11, 2003 9:06 AM > Subject: > > ,cru...@li... > MIME-Version: 1.0 > X-Priority: 3 (Normal) > X-Authenticated-Sender: #000...@gm... > X-Authenticated-IP: [213.68.175.171] > Message-ID: <101...@ww...> > X-Mailer: WWW-Mail 1.6 (Global Message Exchange) > X-Flags: 0001 > Content-Type: text/plain; charset="iso-8859-1" > Content-Transfer-Encoding: 8bit > Subject: [Cruisecontrol-user] Support of a fairly large build process... > Sender: cru...@li... > Errors-To: cru...@li... > X-BeenThere: cru...@li... > X-Mailman-Version: 2.0.9-sf.net > Precedence: bulk > List-Help: > <mailto:cru...@li...?subject=help> > List-Post: <mailto:cru...@li...> > List-Subscribe: > <https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user>, > > <mailto:cru...@li...?subject=subscribe > > > List-Id: <cruisecontrol-user.lists.sourceforge.net> > List-Unsubscribe: > <https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user>, > > <mailto:cru...@li...?subject=unsubscri > be> > List-Archive: > <http://sourceforge.net/mailarchive/forum.php?forum=cruisecontrol-user> > X-Original-Date: Fri, 11 Apr 2003 09:08:33 +0200 (MEST) > Date: Fri, 11 Apr 2003 09:08:33 +0200 (MEST) > > Hello, > we have here a quite large build process already set up with ANT. Now we > would like to use CC for our Nightly Builds and for Continuous > Integration. The > problem for us right now, is that we have already set up a couple of > property > files for each project, in which e.g. the name of the project etc. is > defined. For CC it does not seem possible to use now these property files. > Is this > somehow possible? Any suggestions are greatly appreciated. > Anyway, another issue we have is the support of multiple projects. Our > projects have a special build order, and must be build by using always the > latest > jars of the other components involved. How can we make sure, that > everything > is build in the correct order. It seems to be possible to do this via a > certain time, a build starts, but this is not as good, as we would like to > have > it, because we can not guarantee, that componente 1 takes 5 minutes to > compile > and not say 10 minutes. > > Hints? > > Greets > > Markus > > -- > +++ GMX - Mail, Messaging & more http://www.gmx.net +++ > Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage! > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of TotalView, The > debugger > for complex code. Debugging C/C++ programs can leave you feeling lost and > disoriented. TotalView can help you find your way. Available on major UNIX > > and Linux platforms. Try it free. www.etnus.com > _______________________________________________ > Cruisecontrol-user mailing list > Cru...@li... > https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user |