Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-Id: <CC1A5F26-359D-4D3C-AAA5-CFC5E80B1F18@anyware-tech.com>
From: =?ISO-8859-1?Q?Nicolas_Lalev=E9e?= <nicolas.lalevee@anyware-tech.com>
To: ivy-user@ant.apache.org
In-Reply-To: <8CCED536-BCE8-42BA-A7C4-F743E74BB3D2@iki.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v919.2)
Subject: Re: Continuous integration and deciding whether to build
Date: Fri, 29 Feb 2008 21:40:07 +0100
References: <8CCED536-BCE8-42BA-A7C4-F743E74BB3D2@iki.fi>


Le 29 f=E9vr. 08 =E0 20:24, Juha Ranta a =E9crit :

> Hello,
>
> As an introduction, I have an existing build system that I'm trying =20=

> to improve by using Ivy. I think Ivy is very cool, so big thanks for =20=

> it!
>
> I have a build server with projects checked out from CVS in one =20
> directory like this:
>
> projectA/
> projectB/
> projectC/
> projectD/
> ....
>
> Each project has in its root directory a build.xml and ivy.xml which =20=

> also come from CVS.
>
> Each of these projects can build, tag, etc, itself and finally =20
> publish its artifact to an Ivy repository independently without =20
> directly referencing other projects. Now I'd like to implement a =20
> simple script which polls CVS and builds automatically builds new =20
> artifacts from projects which, well, need to be built. I can quite =20
> easily get a list of these projects with the Ant task buildlist =20
> sorted so that, for example, if A depends on B, B gets built and =20
> published before A. During the buildlist processing, the script goes =20=

> through each of the projects to see if there are any changes in CVS =20=

> and if there are, the project gets built. This works fine except =20
> that there are also the dynamic "latest.integration" revisions in =20
> the ivy.xmls and the script doesn't know if some if the dynamic =20
> revisions have changed by just polling CVS.
>
> I think that my script would work like I wanted it to if it would =20
> trigger a new build if the project has changed in CVS since the last =20=

> build *or* if the dynamic revisions have changed. Therefore I'm now =20=

> wondering what's the best way to check whether the dynamic revisions =20=

> have changed. My script can get to the "static" ivy.xml of the =20
> previous build. It perhaps would work if the script executed =20
> "resolve", "delivered" a new static ivy.xml and then somehow diffed =20=

> the static dependencies of the previous static ivy.xml to the new =20
> static ivy.xml to decide whether a new build should be triggered.
>
> Are the some easy ways to check if the dependencies of the latest =20
> resolved ivy.xml differ from those of a previously resolved ivy.xml? =20=

> Or you think my approach is way off and that I should do it some =20
> other way?


I have no answer but a question :)
It seems strange to me of having a dynamic revision that does not =20
change between two builds. What is the rationale behind it ?

Nicolas