Return-Path: X-Original-To: apmail-ant-ivy-user-archive@www.apache.org Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 779F410057 for ; Mon, 24 Nov 2014 08:52:06 +0000 (UTC) Received: (qmail 37729 invoked by uid 500); 24 Nov 2014 08:52:06 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 37689 invoked by uid 500); 24 Nov 2014 08:52:06 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 37677 invoked by uid 99); 24 Nov 2014 08:52:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Nov 2014 08:52:05 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of hkaiserl@gmail.com designates 74.125.82.45 as permitted sender) Received: from [74.125.82.45] (HELO mail-wg0-f45.google.com) (74.125.82.45) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Nov 2014 08:51:38 +0000 Received: by mail-wg0-f45.google.com with SMTP id b13so11669308wgh.4 for ; Mon, 24 Nov 2014 00:51:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:message-id:date:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=jNPG0sMRSGaAeoDsy6mr7om3m+QCXaOpsJBc7KuRmXU=; b=BIektaln8ZF3TYG1r2SjPzll9LX72ADEzkrZ8turcmfGhaAtVLM/bcRfbyS72vuHt1 z8djP7wqGQM7vTDr/bcw6dLioekAN96cF9oFckV/f4I067+FaeTWwiDODay41cBJVlwC FsVcO2Pw0y4V74sZa1GeiV2EuKFM1NKSOqDZ3/DMbaOwyUbbA8bfkjgpLSGMdnUTDNtG 9h0R0ZRExE9sUOYGYA9LKbgLaUVhye+dEbRO0YOCAfijyH0RzW7Vd6DG891WRERzrdC/ +OR7LH6c7XIsntN3VsMNMK/tNyBaMS0mcRDNd0mQ+ERXzCtKQKHRs9gCTPnMslu5ur/a S1kg== X-Received: by 10.194.156.201 with SMTP id wg9mr31853336wjb.59.1416819097594; Mon, 24 Nov 2014 00:51:37 -0800 (PST) Received: from [10.11.12.164] (p3E9E9443.dip0.t-ipconnect.de. [62.158.148.67]) by mx.google.com with ESMTPSA id h13sm11076266wiw.4.2014.11.24.00.51.36 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Nov 2014 00:51:36 -0800 (PST) From: "hkaiserl@googlemail.com" X-Google-Original-From: "hkaiserl@googlemail.com" Message-ID: <5472F195.10506@googlemail.com> Date: Mon, 24 Nov 2014 09:51:33 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: ivy-user@ant.apache.org Subject: IVY resolve and IVY publish very slow X-Opacus-Archived: none Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello together, I am facing the problem, that my IVY publish into a local file cache is taking "ages". It takes at least 30 seconds to publish a set of max of 3 artifacts. (jar, source, javadoc) Same issue is on IVY resolve. Here it seems to be the up to date check of Ivy to verify if the resources are still the newest. How can I modify the behaviour of this update check? e.g. here it takes sometimes minutes, even if the stuff is already cached. Since we have a multiproject environment with 13 projects IVY eats up following times: 13x 30sec for local publish => 6,5 minutes 13x at least 30sec for resolve => 6,5 minutes So our build is waiting about 10-13 minutes only for IVY. The whole build (incl. IVY) takes about 15-16 minutes. Can someone help me out of the dark how to improve IVY publish and IVY resolve for a local - very fast - build. On our CI jenkins, it is okay - not nice but okay - to take what time. best wishes, hkais