Command Line Snapshot/Label?

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Ryan Breakspear

Command Line Snapshot/Label?

Post by Ryan Breakspear » Wed Apr 07, 2004 2:15 am

Hi,

I've just upgraded to Vault 2.0.1 (2137), and our automated build routine for labeling a version doesn't seem to work. I understand that what were called Labels are now called Snapshots (is this correct?). This new naming convention makes sense, but there doesn't seem a way to take a Snapshot from the command line.

We use a product called Visual Build Pro, which has a wrapper for the SourceGear Vault commands, but I can't get a snapshot to work directly from a command prompt.

Am I doing this all wrong, please help.

Regards

Ryan

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Wed Apr 07, 2004 8:07 am

Ryan:

Let me first answer your question with a question. Why not label the folder/files?

Although, snapshot is not supported in the clc, you could branch and pin to achieve the same results.
Jeff Clausius
SourceGear

Ryan Breakspear

Post by Ryan Breakspear » Tue Apr 13, 2004 4:33 am

I was using Label in the previous versions of Vault, but this no longer works with our automated scripts. I presumed that the label functionallity was now different, so creating a label was no longer what I wanted.

Should the Label functionallity in version 2.0.1 be the same as in 1.x? If so it doesn't seem to work.

Thanks

Ryan

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Tue Apr 13, 2004 7:38 am

Labels were changed dramatically from version 1 to version 2. In version 1, they were essentially pinned branches. This was not compatible at all with how VSS implemented labels, and was not conducive to things like daily builds that were labeled.

We kept the label implementation, but renamed it Snapshots. It is true that this is not available from the command line anymore, but you can get the same behavior by branching and then pinning.

The 2.0 version of labels is a tag applied to a version of a folder or file, much like VSS has.

We recommend the new lightweight 2.0 style labels over the old implemenation of branching the folder for things like daily builds.

Ryan Breakspear

Post by Ryan Breakspear » Tue Apr 13, 2004 9:13 am

Thanks for your message. I have Branched, then Pinned the folders I want in the Vault Client application. The icon looks different to the old style Label, can you confirm that the behaviour will be the same?

We only go through this procedure when we do a full release of the product, and leave the Branched/Pinned folder as a history of the code exactly as it was at the time of release.

Next question. Ahem. When Pinning from the command line, I am required to enter a version number. I can't put in the version number I'd like, what should this be, and how do I find it out? When pinning from within the Vault Client app, I don't need to supply a version number.

Sorry about my lack of knowledge about this subject. I haven't used SourceSafe for years, and the last version control software I used I just created a "Snapshot".

Thanks

Ryan

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Tue Apr 13, 2004 1:04 pm

Ryan Breakspear wrote: Next question. Ahem. When Pinning from the command line, I am required to enter a version number. I can't put in the version number I'd like, what should this be, and how do I find it out? When pinning from within the Vault Client app, I don't need to supply a version number.
Sorry, there doesn't appear to be a way from the command line client to pin at the latest version (without having to specify a version number), nor are there commands to see what the current version of the file is on the server.

Pinning at the latest version would be trivial to fix, but we just released 2.0.2, so it will have to wait for the 2.0.3 boat, which isn't scheduled yet. We do provide the source to the command line, so we could look into this and tell you which lines to fix, and you could recompile it for your uses.

Ryan Breakspear

Post by Ryan Breakspear » Wed Apr 14, 2004 1:42 am

Ok, it isn't a big issue for us to do the snapshot manually, so I can wait for the next version, assuming it will be released in the next few months rather than years?

We only do about one software release here every month but it's nice to have it all automated.

Ryan

Ryan Breakspear

Post by Ryan Breakspear » Thu May 27, 2004 3:58 am

I've just upgraded to 2.0.3, and I can now successfully branch/pin from the command line.

Thanks

Ryan

Post Reply