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 mgitman@gmail.com designates
 209.85.146.178 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=ITDoOtpo/yYQDwyy/IJ0fIpkrawvzzkpAtCVsuMT3JXrjoJ+lR6f3qdNRV6gvC+4kJ
         MnVFS6pB9dk07d3Q1RfzWsTbUeVBQEGwhTmnPdV6n1xFVTmpKh2VUYMs5N47wvIG0btR
         6NhIYSsgWMdkRgZROu3HhDNOaXYdEmN05MYUo=
MIME-Version: 1.0
Date: Sun, 15 Mar 2009 18:53:33 -0700
Message-ID: <7916a6a60903151853xed7c45cye277e2ad104d558@mail.gmail.com>
Subject: trying to configure the Hudson Ivy plugin
From: Mitch Gitman <mgitman@gmail.com>
To: ivy-user@ant.apache.org
Content-Type: multipart/alternative; boundary=00163646d50ccaf254046532b7a9

--00163646d50ccaf254046532b7a9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

I realize I might better be posting this query to the Hudson users mailing
list. And I probably will.

I've installed the Hudson Ivy plugin on Hudson, the CI server.

When I want to configure a particular job (project) to use the Ivy plugin, I
go to the "Post-build Actions" section and check "Trigger the build of other
project based on the Ivy management system." For "Ivy file," I fill in the
path relative to the project root of the ivy.xml file to use. When I do
this, though, I get this error:
HTTP Status 404 - /publisher/IvyBuildTrigger/checkIvyFile

type Status report

message /publisher/IvyBuildTrigger/checkIvyFile

description The requested resource (/publisher/IvyBuildTrigger/checkIvyFile)
is not available.

I've seen an issue in Hudson's issues tracker that describes this same
problem. The issue thread suggests this has been fixed as of March 5:
http://www.nabble.com/-Issue-3100--New---Correctly-configured-ivy.xml-in-project-post-build-action-results-in-HTTP-404-error-td22129981.html

FWIW, I am using the latest version of Hudson. Has anyone else encountered
this? And if so and if you managed to get past it, how? Or was it ignorable?

But then I have a potentially bigger issue with the Hudson Ivy plugin. The
documentation of how to configure it is ambiguous:
http://wiki.hudson-ci.org/display/HUDSON/Ivy+Plugin

The above page suggests one should also check a box, "Build other projects."
And apparently, you need to fill in the names of projects.

I'm going to figure that the checkboxes work like this:

   - "Trigger the build of other project based on the Ivy management
   system": upstream projects; projects that this project depends on
   - "Build other projects": downstream projects; projects that depend on
   this project

Am I interpreting this correctly? If so, I can't help but question the
usefulness of this plugin to begin with since what I really care about is
downstream projects. Perhaps someone who's using Hudson with Ivy can explain
to me the value that the Hudson Ivy plugin provides above and beyond just
manually specifying the dependent projects to build via "Build other
projects."

--00163646d50ccaf254046532b7a9--