Check In Without Working Folder

Post your questions regarding using the Vault and Fortress API in your programs.

Moderator: SourceGear

Post Reply
msikn
Posts: 5
Joined: Fri Jan 20, 2012 1:48 pm

Check In Without Working Folder

Post by msikn » Fri May 03, 2013 3:59 pm

I am writing a task for CruiseControl.NET that needs to check in a file (one of the build outputs) into a folder in Vault that does not have a permanent working folder mapped on the build machine. Is there a way to do this?
Last edited by msikn on Mon May 06, 2013 7:57 am, edited 1 time in total.

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Check In Without Working Folder

Post by lbauer » Mon May 06, 2013 7:40 am

How was the file checked out? Was it checked out to a working folder?
Linda Bauer
SourceGear
Technical Support Manager

msikn
Posts: 5
Joined: Fri Jan 20, 2012 1:48 pm

Re: Check In Without Working Folder

Post by msikn » Mon May 06, 2013 7:53 am

That's a good question, and to answer I'll rephrase my question. I should have asked whether there is a way to check out a file and check in a new version of that file, all without a working folder? :)

I hope my intent is clear - I'd like our build machine to automatically do the checking in and checking out operations as part of the build process without requiring a permanent working folder on the build machine. This would reduce the maintenance burden of our build processes.

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Check In Without Working Folder

Post by lbauer » Mon May 06, 2013 9:14 am

Checkins and checkouts must be done from a working folder.

However you can set the working folder "on the fly" with the Vault Command Line Client:
usage: vault.exe SETWORKINGFOLDER [options] repositoryfolder localfolder

SETWORKINGFOLDER will set the working folder for the specified repository
folder to be the local folder. All future operations on repositoryfolder
will use localfolder as a working folder by default.

Server and authentication information is specified by:
-host host

Hostname of the server to connect to. Can also use "-server".
-ssl

Enables SSL for server connection.
-user username

Username to use when connecting to server.
-password password

Password to use when connecting to server.
-repository repositoryname

Repository to connect to.
This is a list of possible options:

-forcesubfolderstoinherit

Force subfolders to use inherited working folder.
This could be incorporated into your build script.
Linda Bauer
SourceGear
Technical Support Manager

msikn
Posts: 5
Joined: Fri Jan 20, 2012 1:48 pm

Re: Check In Without Working Folder

Post by msikn » Mon May 06, 2013 9:22 am

Ok, thank you. I was hoping for a method without working folders, but this will have to do.

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Check In Without Working Folder

Post by lbauer » Mon May 06, 2013 12:31 pm

For additional Command Line Client help, see our website at http://download.sourcegear.com/misc/vau ... nt/clc.htm. You can also use a commant prompt to cd to the Vault Client directory and type "vault.exe helphtml" to generate the html help. Or "vault help" for more detailed help.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply