The files in the mainline branch are being labeled, I don't understand why?

[ambalboa]

I didn't notice this until today, but the mainline branch has all the labels that were created for a repository in a child branch. When I use the 'Surround SCM' action step, I specify the child branch, the repository, and the items to be label. I was looking to see if I had an option checked which would create a label for the specified branch and the parent branch or mainline also. I didn't found one. I also looked for a promotion option, but nothing. Why is this happening? Thankfully, the mainline branch files are not being modified, but the label I'm creating for the child branch is showing up when I check the history of the mainline branch files? Could it be that I'm using labeling improperly? I'm creating a label indicating the new updated version number. The files in the child branch are being modified, and the version number in Surround is being incremented, as it should be. Can someone tell me what's going on? Thank you.

[kinook]

This sounds like a question for the Surround SCM folks. You can check the 'Show command-line' field on the Options tab of the Surround SCM action to provide with a support incident.

[ambalboa]

But I am using VBP, I am not using Surround to create a label. Still, I'll ask them.

[kinook]

The VBP Surround SCM action calls the Surround SCM command-line program (sscm.exe) to actually perform a Surround SCM command.
http://www.visualbuild.com/Manual/surroundscm.htm

Again, you can check the 'Show command-line' field on the Options tab of the Surround SCM action to provide with a support incident to Seapine.
http://www.visualbuild.com/Manual/surroundoptionstab.htm

[ambalboa]

I may have found the problem. It seems that the label appears (or is created) in the mainline when the file version (set by Surround SCM) in the parent branch and child branch are the same. And this number is incremented every time a file is modified. So if I create a label for a file in the child branch that has a version number of 5 (for example), and that same file has a version number of 1 in the parent branch, then the label is only created for the file in the child branch.

The 'Surround SCM' action step has a version textbox in the Flags tab. It doesn't seem to work, maybe I need to play with it more. According to some web site, if the version number is specified, it is ignored if the filename is not specified. I only type in a "/" or a repository name like "/Source Code" in the items or files to process box to process each file in the repository and create a label for each one, and I have done that successfully. Is what I'm writing in the files to process textbox not specifying a file?

Can anyone tell me how to use the version textbox? I think I need to specify the version number, but do I also need to specify the filename? I guess it makes sense to label only modified files. Can anyone give me some tips? Thanks.

[kinook]

The Version field on the Surround SCM action corresponds with the sscm -v flag. You would need to check the Surround SCM CLI Guide.pdf or Seapine support for more information about Surround SCM labels, versions, or other options.

[ambalboa]

I asked the people in Surround about this issue, got a response and pending another response from them, to clarify the cause. Take a look at it and let me know what you think they mean.

http://www.seapine.com/dcforum/dcboard.php?az=show_topic&forum=124&topic_id=811&mesg_id=811&page=

They take a long time to respond back. With that said, I want to thank the kinook forum support group for their rapid response time. Every time I posted a question, you have responded right back with great feedback. Thanks again.

[FredDavidson]

Hello!

The Seapine User Forums you note in your post (http://www.seapine.com/dcforum/dcboard.php?az=show_topic&forum=124&topic_id=811&mesg_id=811&page=) are designed strictly to be a user-to-user center, where users can share ideas and concepts, and it is not designed for assistance in troubleshooting issues since Seapine Support employees do not normally monitor the Forums. Seapine Software Technical Support can be accessed by following the instructions on our website (http://www.seapine.com/support.html).

If you need further assistance with Surround SCM please feel free to contact Seapine Software Technical Support. We respond to most questions within 4 hours when received during normal business hours following the steps outlined on our website above.

Best Regards,

_______________________________

Fred Davidson
Vice President, Quality and Customer Support

Seapine Software, Inc.
Phone: 513.754.1655
Fax: 513.754.1660
http://www.seapine.com
_______________________________