On Sep 17, 2008, at 9:44 AM, Xavier Hanin wrote:
On Wed, Sep 17, 2008 at 9:36 AM, Hans Dockter <[EMAIL PROTECTED]>
wrote:
On Sep 17, 2008, at 9:25 AM, Xavier Hanin wrote:
On Wed, Sep 17, 2008 at 9:10 AM, Hans Dockter <[EMAIL PROTECTED]>
wrote:
On Sep 17, 2008, at 8:39 AM, Xavier Hanin wrote:
On Wed, Sep 17, 2008 at 6:53 AM, <[EMAIL PROTECTED]>
wrote:
I tried to find out if there are builds on the CI system
http://builds.xoocode.org/ but that URL does not respond.
It's been a long time since I've touched this, and without any
community
catch up, the project is dormant. I may wake it up, but it'd be
better
for
Ivy to rely on an established CI server.
Gradle is hosted at JetBrain's teamcity server: http://
teamcity.jetbrains.com
I really like Teamcity and the hosting is very reliable. They
only host
selected projects. Considering the popularity of Ivy and that
they use
Ivy
under the hood in Teamcity (at least I think so), I suppose that
should
be
no problem. Why not hosting the CI build of Ivy there?
This may make sense. I've quickly browsed the web UI as a guest,
and while
I
get a list of artifacts produced by a build [1], the links for
the zip
artifacts are broken. Does artifact publication usually work
properly?
Yes. For some reason only Gradle seems to have this problem. If
you try it
with the other projects (e.g. Groovy) it works. I have to find out
why it
does not work with Gradle.
Indeed, it works properly for groovy, and the service seems to be
pretty
good. Do you know who I can contact to get our build setup on their
server?
I usually use the email address at the bottom of the Teamcity UI page:
[EMAIL PROTECTED]
- Hans
Xavier
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
--
Xavier Hanin - Independent Java Consultant
BordeauxJUG co leader - http://www.bordeauxjug.org/
Blogger - http://xhab.blogspot.com/
Apache Ivy Creator - http://ant.apache.org/ivy/
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
