Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Users List" <user@ant.apache.org>
Received-SPF: pass (herse.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: best practices - building on multiple os's
Date: Tue, 24 Jul 2007 08:33:35 -0500
Message-ID: 
 <43C7278FD7C46E42A193246BC2FEDA5C08FCA9@PTSCORP-EXCH.pointserve.com>
In-Reply-To: <46A51E52.7050608@apache.org>
Thread-Topic: best practices - building on multiple os's
Thread-Index: AcfNcRaV5tS8CP2JTFe9JMRHkCkMNgAhhlCw
From: "Loehr, Ruel" <rloehr@pointserve.com>
To: "Ant Users List" <user@ant.apache.org>

Nohup might be just the trick, I'll give that a shot.

-----Original Message-----
From: Steve Loughran [mailto:stevel@apache.org]=20
Sent: Monday, July 23, 2007 4:32 PM
To: Ant Users List
Subject: Re: best practices - building on multiple os's

Loehr, Ruel wrote:
> Hoping some others might have some insight, I've googled around for 2
> days but haven't yet found an answer that seems right.
>=20
> =20
>=20
> I have a project which is c++ based and have created an ant wrapper
> around it to checkout, build, build an installer, and publish the
> project.  This part works pretty well.=20
>=20
> The only problem is that it takes 4 hours to build.   2 hours on
> solaris, and 2 hours on windows.


aah, I forgot about windows


> =20
>=20
> The ant build structure is sort of like this:
>=20
> =20
>=20
> 1)       call sshexec and run solaris build
>=20
> 2)       then proceed on to building windows.
>=20
> =20
>=20
> I'd like to get the solaris and windows portion of the builds to run
in
> parallel but have not yet found a good way to do it.   The sshexec
task
> blocks until the solaris portion is done.

1. you could run the solaris build in the background, sshexec the=20
equivalent command as

nohup ant -f project/build.xml release &

you then need to synchronise for the results -setting a file in a shared

directory, anything we can use <waitfor> to poll for.

2. I have heard -but no experience of- anthill pro, which can apparently

do some parallel build-farm work.

similarly, you can set up luntbuild, bamboo or other CI tools to do a=20
scheduled build, so it could do a nightly release, or so

3. the third option is pretty low level, and is more an extension of=20
(1); use smartfrog (disclaimer., I work on it), to deploy ant on the=20
different machines. and choreograph the builds. This is really something

I'd point you at if you are interested in doing cross-platform testing=20
after the builds, where you want to collect the results on a single=20
host, or if you were planning on learning smartfrog anyway.

-steve


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org