ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Metcalf <jeffrey_m_metc...@yahoo.com>
Subject Re: AW: Ivy 2 and CruiseControl integration
Date Tue, 16 Feb 2010 14:22:40 GMT
I actually participated in updating the Ivy2 plugin for Hudson.  It works quite well and may
provide everything you need. If you decide to go the Hudson route, let me know if you run
into limitations. I may be able to provide some help. 

Thanks,

-J

Sent from my iPhone

On Feb 15, 2010, at 10:14, Klaas Prause <klaas.prause@blau.de> wrote:

We used it in the following way:
1. Ant builds a project, if all testing and packaging works fine the artifacts are published
directly from the ANT script
2. in "onsuccess" of CruiseControl we used the ivy plugin to trigger all depend builds. Note
that the trigger is just a modification at the project so that triggers from different projects
result in one build only

It was no problem. Only CruiseControl did not scale good enough so we needed to dump it. Right
now I would never use CruiseControl again, instead use Hudson and write a plugin for it or
buy Bamboo and write a plugin for bamboo. We now use Bamboo and wrote a custom plugin for
it.

Regards Klaas

-----Urspr√ľngliche Nachricht-----
Von: Jimenez Coelho, Juan [mailto:juan.jimenezcoelho@citi.com] 
Gesendet: Montag, 15. Februar 2010 16:05
An: 'ivy-user@ant.apache.org'
Betreff: RE: Ivy 2 and CruiseControl integration

As a matter of fact, I had checked ivyplugins before but my (admittedly superficial) reading
of comments, readmes, etc seemed to indicate that this is a Cruisecontrol publisher plug-in
to be used within <onsuccess>.

This did not look like the right thing.  Before I publish I need to build the project and
report any failures (i.e. console output) on the Cruisecontrol project page.  I have something
working by using <exec>.  Of course all console output is lost.

My latest reading seems to indicate that I might need to wrap Ivy in an Ant script.  I suspect
I would need to do more such as specifying where the repository is located, copy ivy2.jar
to lib directory of ANT, etc).

So, my question really is "has anyone taken the trouble to document all these steps"?  Preferably
the best combination as I suspect there are several ways of achieving this.

Thanks again.

-----Original Message-----
From: Gareth Western [mailto:gareth@garethwestern.com]
Sent: 15 February 2010 14:48
To: ivy-user@ant.apache.org
Subject: Re: Ivy 2 and CruiseControl integration

Thanks very much! I'll try and find some time to play around with this once things cool down
with my current workload.

PS I forgot to link to IvyPlugins in my previous email, but for those who are interested and
don't know how to search: the homepage is http://sourceforge.net/projects/ivyplugins/

On Mon, Feb 15, 2010 at 1:33 PM, Klaas Prause <klaas.prause@blau.de> wrote:
Hi,

we used CruiseControl for CI but switched a year ago to Bamboo. We used the ivypublisher as
base for a customized ivy build trigger plugin in CruiseControl. I found an old version in
our VersionControl. It is attached to the mail. It worked for us, feel free to modify it share
it however you like. I am not sure if the archive works out of the box, you need a build file
(we had a customized ANT build process that does not exist anymore so I deleted the incomplete
build file). I cannot give you much help. In the end it is a documented version of the ivypublisher
fixed to work with a newer version of CruiseControl and ivy.

Regards
Klaas

-----Urspr√ľngliche Nachricht-----
Von: Gareth Western [mailto:gareth@garethwestern.com]
Gesendet: Montag, 15. Februar 2010 14:00
An: ivy-user@ant.apache.org
Betreff: Re: Ivy 2 and CruiseControl integration

We use Bamboo rather than CruiseControl, but I think the problem is
the same: build order.

So far we have 2 solutions to this:

1) A single build project, which checks out the entire code base and
then uses the ivy buildlist [1] task to determine the correct order
for building each module. The disadvantage here is having to check out
everything.
2) Checkout each module individually and build when an SVN commit is
detected. The disadvantage here is that there is no dependency
information, so occasionally a build will fail if a dependency is
unsatisfied.

Ideally there would be a plugin for CruiseControl / Bamboo /
CI-Server-Of-Your-Choice that would work in a similar way to the
buildlist task so that your modules always build in the best order.
Unfortunately I don't think there is yet one for Bamboo. There is a
sourceforge project called "IvyPlugins" that might be able to help you
with CruiseControl, but I haven't tried it myself.

Cheers,

Gaz

[1]
http://ant.apache.org/ivy/history/latest-milestone/use/buildlist.html

On Mon, Feb 15, 2010 at 12:52 PM, Jimenez Coelho, Juan
<juan.jimenezcoelho@citi.com> wrote:
We have been using CruiseControl for the past 4 years and have a very large number of projects
being built using both Ant and Maven.

My team is now experimenting with Ivy and I would like to test the builds from CruiseControl.
 As yet, I have not found any page or news item describing a good way of doing this.  Could
someone please point me in the right direction?

Thanks

Juan





      

Mime
View raw message