Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: <msmith39@ups.com>
To: <ivy-user@ant.apache.org>
Date: Tue, 14 Oct 2008 11:43:26 -0400
Subject: Ivy latest.integration
Thread-Topic: Ivy latest.integration
Thread-Index: AckuE5jqjjkG3oA/QVOtQyoGzNoczw==
Message-ID: 
 <E50903485626F14497ABFA0519902DFC01EF2F45F7@gaalpsvr036f.us.ups.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_E50903485626F14497ABFA0519902DFC01EF2F45F7gaalpsvr036fu_"
MIME-Version: 1.0

--_000_E50903485626F14497ABFA0519902DFC01EF2F45F7gaalpsvr036fu_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,

I'm new to Ivy Publisher and it's currently used with Cruise Control v2.5. =
 The scripts are working fine and the source control tool is PVCS Version M=
anager 8.1.3.

All builds are fine as long as we are monitoring the tip versions.  But thi=
s is now getting out of control and we need to apply a version label to the=
 artifacts and build based on that.  I noticed in the scripts the revision =
is set to:  rev=3D"latest.integration".  Is there a way we can set it to: r=
ev=3D"DEV-10.10" or any assigned version label?

We have about 48-50 components and there are inter-dependencies with severa=
l.  I want to institute branching as well, thus also introduces floating th=
e label when check-in's take place and we could be on 2-3 different build l=
abels at the same time.

Any help would be greatly appreciated.


Michael V. Smith (aka Smitty)
UPS Deployment Management Team
Visibility Systems
Office: (678) 746-7247


--_000_E50903485626F14497ABFA0519902DFC01EF2F45F7gaalpsvr036fu_--