Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (nike.apache.org: domain of joshua.tharp@gmail.com
 designates 209.85.211.199 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=n3lKA8FVgk4XzMxTzPZ5CV46XwSal4gK9+9yGHD29KBpSmDhyYpLBdOuUztDW0JLfR
         biGCMm65CNh/G2nmMaHoTz++mX8rJkAsd0BiwriUmgaGWRwDJcYUfKHFfU0SjHyk4wC8
         wy2lkfaai+v98Gk83ScFzNyAai4XpPaQr5tZw=
MIME-Version: 1.0
Sender: joshua.tharp@gmail.com
In-Reply-To: 
 <34721A41A7BCF54ABC3B116219A8C1C2057EC4913F@NP1EXCH012.corp.halliburton.com>
References: <8d2e5b750908070834ga70c7f7t38c70e2a3fb6fce5@mail.gmail.com>
	 <7916a6a60908070842s6098a844wb4407854340a3581@mail.gmail.com>
	 <8d2e5b750908070937y2ad1a94ayf584c91b10f2780c@mail.gmail.com>
	 <7FE5E452E16A8D4186AAD00EE4532047212F15192B@prodmail2.austx.zilliant.com>
	 <7916a6a60908070952v11ae59a2q91d0d8b50ee882e7@mail.gmail.com>
	 <34721A41A7BCF54ABC3B116219A8C1C2057EC4913F@NP1EXCH012.corp.halliburton.com>
Date: Fri, 7 Aug 2009 13:10:53 -0700
Message-ID: <d7681c140908071310m379d4071y2af8ab5ebc5d0bb9@mail.gmail.com>
Subject: Re: Ivy feedback mechanisms for spawning builds...
From: Joshua Tharp <joshua-tharp@alumni.calpoly.edu>
To: ivy-user@ant.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I use the Hudson Ivy plugin, and it does figure out both the upstream
and downstream dependencies from the ivy.XML files. What it doesn't do
(or at least I haven't figured it out yet) is not build a module when
you have multiple dependencies that all lead to the same one. For
example, if C depends on A and B and B also depends on A, then when A
is updated Hudson will likely build C twice (once when A is complete
and again when B is rebuilt.

On Friday, August 7, 2009, Shawn Castrianni
<Shawn.Castrianni@halliburton.com> wrote:
> I think what is being asked is how to enhance the CI system so that not o=
nly does it detect changes to the SCM system (which would obviously require=
 a rebuild), but to also detect changes in that module's dependencies in th=
e repository since a change in a dependency should also require a rebuild. =
=A0So what methods or best practices have been developed to have a CI syste=
m check if a module's dependencies have changed since last time it was buil=
t to cause a rebuild?
>
> This might be more of a "pull" technique. =A0The "push" technique might b=
e more of what was already stated in this thread of having an extra step at=
 the end of a build to automatically trigger any other module that has a de=
pendency on the module just built.
>
> ---
> Shawn Castrianni
>
> -----Original Message-----
> From: Mitch Gitman [mailto:mgitman@gmail.com]
> Sent: Friday, August 07, 2009 11:53 AM
> To: ivy-user@ant.apache.org
> Subject: Re: Ivy feedback mechanisms for spawning builds...
>
> OK, I understand what's going on now. One thing to keep in mind is the
> distinction between upstream/dependency projects and downstream/dependent
> projects. Obviously, an ivy.xml tells you only about its dependencies. My
> understanding, though, (and I could be wrong about this) is that the Huds=
on
> Ivy plugin is able to figure out the downstream path. I'd asked about as
> much in this thread and got an affirmative:
> http://www.nabble.com/trying-to-configure-the-Hudson-Ivy-plugin-td2253081=
7.html
>
> Frankly, I haven't found much value in having a plugin automatically figu=
re
> out which projects to build once one project has built. I've been fine to=
 do
> that manually. But I recognize some people may find value in that.
>
> On Fri, Aug 7, 2009 at 9:41 AM, Hilton, Chris <Chris.Hilton@zilliant.com>=
wrote:
>
>> I can't tell if you've considered this already, but have you looked at t=
he
>> Ivy plugin for Hudson?
>>
>> http://wiki.hudson-ci.org/display/HUDSON/Ivy+Plugin
>>
>> Apparently it looks at an ivy file in a project and handles building
>> dependencies, though I haven't tried it.
>>
>> Chris
>>
>> > -----Original Message-----
>> > From: Kevin Gann [mailto:kaygee@gmail.com]
>> > Sent: Friday, 07 August, 2009 11:38
>> > To: ivy-user@ant.apache.org
>> > Subject: Re: Ivy feedback mechanisms for spawning builds...
>> >
>> > Maybe I mis-understood but... I've built the model that you illustrate=
.
>> > :)
>> >
>> > version control system commit --> CI server build --> Ivy publish to
>> > shared
>> > repository
>> >
>> > The problem comes with other projects within VCS which I'd like rebuil=
t
>> > because a new artifact has been published. With my current knowledge I
>> > could
>> > configure Hudson to use a "build trigger" and build after another buil=
d
>> > takes place and utilize latest.integration (or similar) for the
>> > revision.
>> >
>> > Like I said... it feels wrong to have Hudson hold that configuration,
>> > but I
>> > suppose if CI is only monitoring VCS how else would it know? A hack
>> > would be
>> > to have CI monitor the share which holds the artifacts I want to
>> > rebuild
>> > with.
>> >
>> > On Fri, Aug 7, 2009 at 8:42 AM, Mitch Gitman <mgitman@gmail.com> wrote=
:
>> >
>> > > Kevin, it sounds like you're thinking about the problem in the wrong
>> > way.
>> > > Leaving aside the case of the Ivysvn resolver where Subversion is
>> > doubling
>> > > as an Ivy resolver, your CI server should really be the party
>> > responsible
>> > > for publishing to your shared Ivy repository. The thing that's
>> > triggering
>> > > the CI server is commits to the version control system. This is the
>> > typical
>> > > relationship because it works and makes sense.
>> > >
>> > > Illustrated like so:
>> > > version control system commit --> CI server build --> Ivy publish to
>> > shared
>> > > repository
>> > >
>> > > On Fri, Aug 7, 2009 at 8:34 AM, Kevin Gann <kaygee@gmail.com> wrote:
>> > >
>> > > > I'm trying to figure out how to tell my CI system in an elegant wa=
y
>> > that
>> > > an
>> > > > artifact published to my Ivy repository has changed. Right now I
>> > > > artificially give this feedback using Hudson which forces a build
>> > to be
>> > > > executed once a library is published which a project -------------=
---------------------------------------------------------
> This e-mail, including any attached files, may contain confidential and p=
rivileged information for the sole use of the intended recipient. =A0Any re=
view, use, distribution, or disclosure by others is strictly prohibited. =
=A0If you are not the intended recipient (or authorized to receive informat=
ion for the intended recipient), please contact the sender by reply e-mail =
and delete all copies of this message.
>