Re: How costly if we are creating tags for every continuous build?

We use Hudson as our continuous build engine and create a tag for each
build. As Andy L stated, tags are cheap. They're fast (takes less than
a second to create) and take almost no disk space.

Although many sites don't create Subversion tags for each build, Our
developers and QA engineers prefer tagging because they know the
Hudson build number and not the Subversion repository revision number
that was used for the build.

The main problem with tagging for each build is that you will get
thousands of build tags and maybe a few dozen actual release tags.
That makes finding the release tag much harder to find a release tag
you may be looking for.

To get around this problem, instead of putting our tags directly under
the "tags" directory we use a tags/REL for release tags and a tags/DEV
for the build tags. That keeps all of our build tags out of the way of
our actual release tags.

On Mon, Mar 30, 2009 at 5:12 PM, baz themail <bazthemail_at_gmail.com> wrote:
> Hi,
>
> I would like to create tags for every continuous build and would like to
> know how "costly" in terms of disk space and SVN server usage. Can anyone
> give some advice on this subject?
>
> I understand that in SVN, creating tags of a branch is no different than
> copying a branch. How much disk space will it take? For example, if my trunk
> is about 100MB, then how big will the tag/label?
>
> If we have hundreds of tags, will it slow down the SVN server?
>
> Thanks. A.
>

-- 
--
David Weintraub
qazwart_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1499018
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].