Return-Path: 
 <ivy-user-return-4464-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: (qmail 73088 invoked from network); 23 Dec 2008 10:17:51 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 23 Dec 2008 10:17:51 -0000
Received: (qmail 8830 invoked by uid 500); 23 Dec 2008 10:17:50 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 8804 invoked by uid 500); 23 Dec 2008 10:17:50 -0000
Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@ant.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@ant.apache.org>
List-Post: <mailto:ivy-user@ant.apache.org>
List-Id: <ivy-user.ant.apache.org>
Reply-To: ivy-user@ant.apache.org
Delivered-To: mailing list ivy-user@ant.apache.org
Received: (qmail 8793 invoked by uid 99); 23 Dec 2008 10:17:50 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Dec 2008 02:17:50 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy)
Received: from [68.142.200.146] (HELO web30803.mail.mud.yahoo.com)
 (68.142.200.146)
    by apache.org (qpsmtpd/0.29) with SMTP; Tue, 23 Dec 2008 10:17:42 +0000
Received: (qmail 17866 invoked by uid 60001); 23 Dec 2008 10:17:21 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
  b=sW0TiXFFdpawjIHfIgdUtZOxN0mM0aBgp5yaajPQi+pXwJOdM6PeuHOaQLEmwcCC2qI51DjaHUG760hYlPJBqxA9zkqOf6AvCFn14oQoXd9F/U971sXFjt0F1BUm1ziN8l+RpcPTeU7uf4ir5P1EenHFBIskx+Ot9fGKUVehgNE=;
X-YMail-OSG: 
 YeKKAwYVM1mAV4cVldBPy7UOX1h_ScjIT3izZin1Jj0da.KE28CJl7grvrjpCXccdKOSX.QMzTbcDbAB1fhEKl9HakQJLOzy.Hk0RfHw860Byen4FpC.lejnW5QfkwndrUBZnZhe6NzGmVGfMEsGzurlu253k4eFGmkQupAs.WIRh7N.Rep8COAnTiHILpuB1POoziYbnYAuM4dtcESyBezSG4W0atBD
Received: from [87.65.68.126] by web30803.mail.mud.yahoo.com via HTTP;
 Tue, 23 Dec 2008 02:17:21 PST
X-Mailer: YahooMailRC/1155.45 YahooMailWebService/0.7.260.1
References: <giqc8i$6d3$1@ger.gmane.org>
Date: Tue, 23 Dec 2008 02:17:21 -0800 (PST)
From: Maarten Coene <maarten_coene@yahoo.com>
Subject: Re: TeamCity dependency tracking
To: ivy-user@ant.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Message-ID: <65191.16325.qm@web30803.mail.mud.yahoo.com>
X-Virus-Checked: Checked by ClamAV on apache.org

I don't think this is possible at the moment with Ivy.
Please open a JIRA feature request

Maarten




----- Original Message ----
From: Tom Widmer <tom.widmer@googlemail.com>
To: ivy-user@ant.apache.org
Sent: Tuesday, December 23, 2008 10:50:09 AM
Subject: TeamCity dependency tracking

Hi all,

I'm using a TeamCity build server as an Ivy repository for our build artifacts, and it works very well for the job except for tracking dependencies when using a varying build version, like 'latest.release'. To fix the problem, I need to be able to pass different log in credentials for the ivy.xml files to the artifacts. I have a resolver for the repo like this:

<url name="teamcity" latest="latest-time">
            <ivy pattern="${teamcity.ivy.repo.root}/[module]::([branch]-)main/[revision]/ivy.xml" />
            <artifact pattern="${teamcity.ivy.repo.root}/[module]::([branch]-)main/[revision]/[artifact](.[ext])" />
        </url>

I have:

<credentials host="build" realm="TeamCity"
      username="${teamcity.auth.userId}"
      passwd="${teamcity.auth.password}"/>

but obviously those credentials are used for both the ivy.xml files and the artifacts. Is there any way to specify different credentials for the ivy.xml files?


Background:

TeamCity has a cunning system of tracking dependencies between builds by providing build-specific TeamCity log in credentials to your ant build script in a couple of properties (though Hudson's system of fingerprinting is just as cunning, and would avoid the problem I'm having). Anything downloaded with those credentials during the build gets logged by TeamCity as a dependency of the build. I use this to have automatic tracking of any dependencies that Ivy downloads from TeamCity (the TeamCity UI allows you to navigate to dependency builds, prevent them being cleaned up automatically, etc.).

So, what's the problem? I recently added a nightly regression testing build that always builds against the latest build, using latest.release. Unfortunately, this causes the build to download the ivy.xml file from every single build that exists on the server in order to work out which is the latest. So the regression testing build appears to depend on every single build (though you can tell the real build by looking for the build where more than 1 artifact is a dependency).

I've made it workable by disabling dependency cleanup prevention for that build (so at least the regression test doesn't prevent automatic cleanup of old, unused builds), but it would still be nice to prevent every single ivy.xml file being listed as a dependency! Two possible fixes:

1. Persuade Ivy to download ivy.xml files only using standard credentials, so those downloads won't be tracked.
2. Persuade TeamCity to ignore downloads of ivy.xml files using the build tracking credentials.

I can't see a way to do 2, but does anyone know how to do 1?

Perhaps this is a feature request - some way to bind credentials to things other than just hosts.

Thanks,

Tom