Re: [Draconet-users] Avoiding premature builds with CVS

[Scott Hernandez]

Title: Avoiding premature builds with CVS

It actually sleeps for a minute (the time is configurable via the quietperiod) after it sees the first change. When it wakes it looks to see if there were more changes, if so, the cycle is repeated. This goes on until there are no more changes. Then the build actually works.   Give it a try, I think you will find that this does in fact work as you would hope.   see http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/draconet/draco/service/BuildRunner.cs?rev=1.6&content-type=text/vnd.viewcvs-markup for the CheckForChanges method to see the details. ----- Original Message ----- From: Alexis Smirnov To: '[EMAIL PROTECTED]' Sent: Wednesday, March 26, 2003 9:17 AM Subject: [Draconet-users] Avoiding premature builds with CVS Hello, While working on a large-scale project it is not uncommon to spend a few minutes doing CVS commits. This usually happens when one commits many files to several projects and needs to provide different comments to different sets files. I understand Dcaro.NET launches the build the moment it finds the repository changed. So is it possible guard a complex commit to avoid Draco.NET launching the build in the middle of commit session? Thanks, Alexis weblog: http://radio.weblogs.com/0112946