RE: Labelling under Surround SCM (WAS Re: [Ccnet-devel] New support for Surround SCM)

[Yan S. <Sha...@se...>]

Hello Thibaut,
=20
The CCNet integration was not introduced until Surround SCM 4.1 and thus =
will not function with an earlier version of Surround SCM. You also need =
to be running CCNet 1.0.
=20
Your suggestion of creating snapshot branches as labels is possible and =
we will take a closer look at this issue when designing enhancements to =
the CCNet integration component.=20
=20
Creating snapshot branches should not cause any performance issues with =
Surround SCM 4.0 or newer, since snapshot branches are marked as cache =
on demand by default. If a branch is marked as cache on demand, the =
server does not load the branch into memory until it is accessed. After =
an hour if the branch has not been referenced the memory is cleared. In =
a scenario where you create nightly snapshots and nightly builds, you =
should not experience any performance issues, since I presume that old =
snapshot branches will not be accessed frequently. Another way to handle =
that situation would be to turn off the "Activate" flag on the snapshot =
branches which are old and no longer used. When a branch is not active, =
it is not cached on the server and does not consume memory resources, =
however, users will not be able to access the contents of that branch =
until the "Activate" flag is enabled.
=20
Please let me know if you have any additional questions or concerns.
=20
Regards,
=20
Yan Shapochnik
Software Engineer
Seapine Software
www.seapine.com
=20
________________________________

From: Thibaut Barr=E8re [mailto:thi...@gm...]=20
Sent: Thursday, February 09, 2006 2:58 AM
To: Yan Shapochnik
Cc: ccn...@li...
Subject: Re: Labelling under Surround SCM (WAS Re: [Ccnet-devel] New =
support for Surround SCM)


Hello Yan et al.,=20



	Just as a reminder, Surround SCM 4.1.0 was just released last week on =
January 30th, 2006.


My customer is currently using 4.0 and the switch is not yet about to be =
done. I've read on the Surround SCM sourcecode provider doc that it's =
tested against v4.1, do you think I'll have issues if I use it against =
v4.0 ? (I don't need a contractual note, just a rough idea, to see if =
I'd better wait for the move to 4.1 or if I can start implementing CCNet =
right now)



	We have not implemented the labeling mechanism as we advise our not to =
use that approach. We recommend using branches in place of labels. =
Surround SCM does support labels and we will likely include label =
support in a later release of our CCNet integration.


I've read this recommendation and we follow it here: we use branches =
(snapshots branches to be accurate) instead of labels. I was referring =
to "label" as it's the common name used for marking/tagging sources in =
ccnet.

Would it make sense to implement the labelling part of Surround CCNet =
(ie. the LabelSourceControl method in Surround.cs) by actually creating =
snapshot branches ? This way users could keep track of their build =
numbers in an automated fashion.

Also, do you think that creating a snapshot branch at each build for =
each CCNet project could lead to performance issues ? (ie: is something =
like 300 snapshots branches on a given repository something to be =
avoided ?)

regards and thanks again for your work

Thibaut
--
[blog] http://www.dotnetguru2.org/tbarrere=20