ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Becheanu" <daniel.beche...@gmail.com>
Subject Re: buildnumber Ant task & automated updates of ivy.xml
Date Wed, 19 Nov 2008 21:39:44 GMT
If you are using cruisecontrol you can use
http://cruisecontrol.sourceforge.net/main/configxml.html#antpublisher

which is automatically publishing properties described in below link

http://cruisecontrol.sourceforge.net/main/configxml.html#buildproperties (
look at label property)

Daniel

On Wed, Nov 19, 2008 at 3:33 PM, Mitch Gitman <mgitman@gmail.com> wrote:

> Quick replies inline.
>
> On Wed, Nov 19, 2008 at 8:30 AM, Shawn Castrianni <
> Shawn.Castrianni@halliburton.com> wrote:
>
> > I started off using the buildnumber task to let IVY control the build
> > number for CI, but then found it difficult to tell the CI tool what the
> > version number was that IVY selected.  Obvioulsy, it is better if the
> > version number used by CI matches the version used by IVY.  Therefore, I
> > switched to NOT use the buildnumber task and let the CI tool choose the
> > number and pass it to IVY as a environment variable or ant property that
> can
> > be passed into the ant command line.  When developers do their own builds
> > outside of the CI system, the buildnumber is hardcoded to "LOCAL".
> >
> Hmm, so how is your CI tool figuring out the build number so that it can
> pass it to Ivy?
>
> >
> > As far as updating XML, the xmltask from oops consultancy is perfect.  I
> > have been able to do everything I need for parsing and editing with that
> > task.
> >
> I'll make sure to check this out some time. Thanks.
>
> >
> > ---
> > Shawn Castrianni
> >
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message