ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Castrianni <Shawn.Castria...@halliburton.com>
Subject RE: buildnumber Ant task & automated updates of ivy.xml
Date Thu, 20 Nov 2008 16:46:54 GMT
If the source comes from CVS, we tag it.  If the source comes from SVN, I use the CI system
to set an ANT property based on what subversion revision was checked out which gets resolved
and stored into the ivy.xml file for publishing.  Then any published build will contain the
ivy.xml file which contains the revision number from subversion from which it was built. 
Once nice feature of subversion.

---
Shawn Castrianni

-----Original Message-----
From: Niklas Matthies [mailto:ml_ivy-user@nmhq.net]
Sent: Thursday, November 20, 2008 7:27 AM
To: ivy-user@ant.apache.org
Subject: Re: buildnumber Ant task & automated updates of ivy.xml

On Thu 2008-11-20 at 11:10h, Jonathan Oulds wrote on ivy-user:
:
> As an example we have our project source under SVN.  Our CI inspects the
> project then builds and publishes if it detects any changes.  however if
> we hard coded the revision number into the ivy file then our CI machine
> would have to update the ivy file with the new version and do a commit.
>
> That didn't sound like a good idea to us, so we headed down the route of
> not having the version numbers specified in the ivy file and only
> resolving the correct version number upon delivery.  Our CI machine will
> auto increment the build number, when a module changes significantly we
> do a special build of the module updating the major or minor version.

I'm curious: Given a build number, how do you later find the
corresponding sources in SVN? Does the CI system tag the sources
with the auto-incremented build number?

-- Niklas Matthies

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

Mime
View raw message