Return-Path: Delivered-To: apmail-ant-user-archive@www.apache.org Received: (qmail 70598 invoked from network); 1 Jun 2009 15:25:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Jun 2009 15:25:56 -0000 Received: (qmail 50602 invoked by uid 500); 1 Jun 2009 15:26:08 -0000 Delivered-To: apmail-ant-user-archive@ant.apache.org Received: (qmail 50529 invoked by uid 500); 1 Jun 2009 15:26:07 -0000 Mailing-List: contact user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list user@ant.apache.org Received: (qmail 50519 invoked by uid 99); 1 Jun 2009 15:26:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jun 2009 15:26:07 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of qazwart@gmail.com designates 209.85.221.116 as permitted sender) Received: from [209.85.221.116] (HELO mail-qy0-f116.google.com) (209.85.221.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jun 2009 15:25:57 +0000 Received: by qyk14 with SMTP id 14so11633033qyk.14 for ; Mon, 01 Jun 2009 08:25:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=56cQmp8CjZbbrJBALSbZ5HQn+/dBqguPW6MIJ9TE1Y4=; b=fGf7vWKrMA9EG2GRo4PeHp8rfChUQaEFkUyC69rPW66QFYqyH5OO1G8WS5mvGNbxPP VG5FZN0khZRy5Ju2iT4bbpiBEQTw9VyI1Qy2YIUlX47C5gV+vQ9GNKGBOXmZcE5euHcC xPth/ZmukJ2TuWDj8/3okLEgj5uRcpHeo+BwA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=g3ZQEFeQ5Mrm3bGmiV1RxPvKMUUdFjRMONQfRDf82yv/pYYt5eCbtaDa8/jLdKeWFs VLkTV03/UAZDd0EUj5BsW3VvD1i3k6bjbggC/azZ0s3EiFGHmjYSEtCLyhPUk0jl7Z0t dbkBq5tb3gA45kzGdG6P0NCR5GUtvFJE6IE/k= MIME-Version: 1.0 Received: by 10.224.29.8 with SMTP id o8mr5678939qac.115.1243869556533; Mon, 01 Jun 2009 08:19:16 -0700 (PDT) In-Reply-To: <515521.53234.qm@web65708.mail.ac4.yahoo.com> References: <915397.77756.qm@web65713.mail.ac4.yahoo.com> <515521.53234.qm@web65708.mail.ac4.yahoo.com> Date: Mon, 1 Jun 2009 11:19:16 -0400 Message-ID: Subject: Re: Use of Sleep From: David Weintraub To: Ant Users List Content-Type: multipart/alternative; boundary=0015175ce014106b1a046b4af3a2 X-Virus-Checked: Checked by ClamAV on apache.org --0015175ce014106b1a046b4af3a2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On Mon, Jun 1, 2009 at 10:39 AM, Eric Fetzer wrote: > A good piece of the time, David, is allocated to check out of A LOT of > code. It also ftp's some very large files over a WAN. As I take over these > builds, I will be digging further in where all the time is going, but for > now, I'm just trying to get rid of totally unnecessary aspects of the build. I normally don't have Ant do my checkouts since you first have to checkout the build.xml file to do the initial checkout. We use Hudson for our continuous integration, and Hudson handles the checkouts for us. That way, I don't even have to define a checkout task in our build.xml file. (See < http://hudson.dev.java.net/>). You might want to switch from checkouts to updates since updates only update changed files, and don't checkout everything from scratch again. There are specific Ant checkout tasks for various version control systems, but I usually don't find them any faster than . Unless the task runs in the background (spawn="true"), it should wait for the task to complete. That means you shouldn't be having tasks to wait for the checkout to complete. You normally run an task in the background when you're doing things like starting up a server, so you can run your tests. Otherwise, the default is to wait for the command to complete. BTW, there is a "timeout" parameter for the task that can help kill an otherwise lollying program, but it has a bit of trouble on Windows sytems. Best of luck speeding up your build. When I first got to my current job, builds took 30+ minutes to complete. I rewrote the build.xml file from scratch, and speeded it up to only "12 minutes". Meanwhile, we've pulled projects out of our main build, and each one of these build in under 2 or 3 minutes. The "big" project still takes about 9 minutes to build. Not where I'd like it, but much better than it was before. My experience shows that when builds take forever, developers simply don't test as well, and your code gets sloppier. -- David Weintraub qazwart@gmail.com --0015175ce014106b1a046b4af3a2--