using ant to tag a cvs repository

[Mark Lybarger <Ma...@CBC-Companies.com>]

we're using ant tasks to do our qa/production builds. it pulls a branch/tag from cvs and does what it needs to build the artifact.  currently, we're not "tagging" that build so that we can re-pull that exact copy out of cvs. i'm not explictly familiar with cvs, so, two questions.  is tagging what i want to use, or a branch? i don't really want to branch each time we do a qa build.  does anyone have an example of a ant cvs task that does what i'm after? here's what we currently use to do the build:

		<cvs cvsRoot=":pserver:${cvs.login.username}:${cvs.login.password}@${cvs.server.ip}:${cvs.server.path}" 
			package="${cvs.module}" tag="${tag}" dest="${cvs.module.dest}" />

much thanks!
~mark

Re: using ant to tag a cvs repository

[Marcel Stör <ma...@frightanic.com>]

Mark Lybarger wrote:
> we're using ant tasks to do our qa/production builds. it pulls a
> branch/tag from cvs and does what it needs to build the artifact. 
> currently, we're not "tagging" that build so that we can re-pull that
> exact copy out of cvs. i'm not explictly familiar with cvs, so, two
> questions.  is tagging what i want to use, or a branch? i don't
> really want to branch each time we do a qa build.  does anyone have
> an example of a ant cvs task that does what i'm after?

I guess that would be:
<cvs command="rtag ${yourTag} ${yourProject}" />

Regards,
Marcel

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org

Re: using ant to tag a cvs repository

["mail.laconiadatasystems.com" <we...@laconiadatasystems.com>]

Mark-

A branch is a physical separation of your source from a known point known as
the trunk so that anything that you checkin or checkout within the fileset
identified as branch will not physically touch any of the files in the
trunk..branches are merged into the trunk

A tag is To create a snapshot of the current sources for later use, use the
CVS tag command. The tag command generates a symbolic tag that is bound to
each of the current revisions in your local copy of the module
A tag is used to give you a snapshot of n items in your sourcetree at a
given point in time

Hope this helps,
Martin
NB:
Here are the references I have used
http://www.fisica.uniud.it/~glast/sw/cvs/cvsintro.html
http://www.cvshome.org


----- Original Message -----
From: "Mark Lybarger" <Ma...@CBC-Companies.com>
To: "Ant Users List (E-mail)" <us...@ant.apache.org>
Sent: Tuesday, August 24, 2004 7:29 AM
Subject: using ant to tag a cvs repository


we're using ant tasks to do our qa/production builds. it pulls a branch/tag
from cvs and does what it needs to build the artifact.  currently, we're not
"tagging" that build so that we can re-pull that exact copy out of cvs. i'm
not explictly familiar with cvs, so, two questions.  is tagging what i want
to use, or a branch? i don't really want to branch each time we do a qa
build.  does anyone have an example of a ant cvs task that does what i'm
after? here's what we currently use to do the build:

<cvs
cvsRoot=":pserver:${cvs.login.username}:${cvs.login.password}@${cvs.server.i
p}:${cvs.server.path}"
package="${cvs.module}" tag="${tag}" dest="${cvs.module.dest}" />

much thanks!
~mark




----------------------------------------------------------------------------
----


> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org

Re: using ant to tag a cvs repository

[Ivan Ivanov <ra...@yahoo.com>]

--- Mark Lybarger <Ma...@CBC-Companies.com>
wrote:

> we're using ant tasks to do our qa/production
> builds. it pulls a branch/tag from cvs and does what
> it needs to build the artifact.  currently, we're
> not "tagging" that build so that we can re-pull that
> exact copy out of cvs. i'm not explictly familiar
> with cvs, so, two questions.  is tagging what i want
> to use, or a branch? 

I think you need tagging. Branching is needed when a
concurrent development is needed. The exact cvs
command for tagging (using command line cvs client)
cvs rtag tag_name.

The corresponding ant script is
<cvs command="rtag tag_name"/>

> i don't really want to branch
> each time we do a qa build.  does anyone have an
> example of a ant cvs task that does what i'm after?

Yes, <cvs> task. it supports command or commandline
attribute, which copy closely the commands of the
commmand-line cvs client.

HTH Ivan

P.S. One example when branching is needed is when you
release a build say buildA, then start to code the
next release say buildB, but some bug requests come
for buildA. You can not fixed them in the current CVS
HEAD since it contains the half-ready buildB (that
will be realeased in the future). So you branch make a
branch for buildA and fix the bug there. You can later
(when buildB is ready) merge the branch for buildA
with the main trunk.

P.P.S. You create a branch from a tag with the command
cvs rtag -b tag_name

> here's what we currently use to do the build:
> 
> 		<cvs
>
cvsRoot=":pserver:${cvs.login.username}:${cvs.login.password}@${cvs.server.ip}:${cvs.server.path}"
> 
> 			package="${cvs.module}" tag="${tag}"
> dest="${cvs.module.dest}" />
> 
> much thanks!
> ~mark
> 
> >
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> user-unsubscribe@ant.apache.org
> For additional commands, e-mail:
user-help@ant.apache.org



		
_______________________________
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.
http://promotions.yahoo.com/goldrush

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org