Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (athena.apache.org: domain of
 Shawn.Castrianni@halliburton.com designates 34.254.16.16 as permitted sender)
From: Shawn Castrianni <Shawn.Castrianni@halliburton.com>
To: "'ivy-user@ant.apache.org'" <ivy-user@ant.apache.org>
Date: Fri, 15 Feb 2008 11:09:03 -0600
Subject: ivy integration with automated build tools
Thread-Topic: ivy integration with automated build tools
Thread-Index: Achv9cogqoAUmedlRm++f3oO9FHrzA==
Message-ID: 
 <745B9EDF57802349B13F90E4E0B4B86C3B92428B02@HOUEXCH012.corp.halliburton.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_745B9EDF57802349B13F90E4E0B4B86C3B92428B02HOUEXCH012cor_"
MIME-Version: 1.0

--_000_745B9EDF57802349B13F90E4E0B4B86C3B92428B02HOUEXCH012cor_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I have my standalone ivy builds working great such that any developer can b=
uild and retrieve dependencies.  However, now I am trying to get automated =
builds going for continuous integration, scheduled nightly builds, etc.  I =
was curious what people out there are using.  I always run into the problem=
 of coordinating the automated build systems build numbers and ivy's build =
numbers.  It would be great if they could be the same such that a developer=
 could look at the automated build website and see builds with numbers that=
 match the number in the ivy repository.

I also see overlap in functionality between ivy and automated build systems=
 with dependency management, publishing, and promotion.  I have all of that=
 working with ivy and am wondering if I just ignore those aspects of the au=
tomated build system in favor of ivy?

---
Shawn Castrianni
CM Lead Architect
Landmark
Halliburton Drilling, Evaluation and Digital Solutions Building 2
2101 City West Blvd.
Houston, TX  77042
Work:  713-839-3086
Cell:  832-654-0888
Fax:  713-839-2758

----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and pri=
vileged information for the sole use of the intended recipient.  Any review=
, use, distribution, or disclosure by others is strictly prohibited.  If yo=
u are not the intended recipient (or authorized to receive information for =
the intended recipient), please contact the sender by reply e-mail and dele=
te all copies of this message.
--_000_745B9EDF57802349B13F90E4E0B4B86C3B92428B02HOUEXCH012cor_--