ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Oulds <>
Subject Re: buildnumber Ant task & automated updates of ivy.xml
Date Thu, 20 Nov 2008 14:00:38 GMT
At present we tag our sources.

But we are at an early stage of moving over to Ivy so I'd be interested 
to hear the experiences of others.  Have others found this approach a 
particularly bad / good idea, do others do anything different if so why?

Niklas Matthies wrote:
> 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

View raw message