I have 2 requests for under the heading of TFS:
First, there is no action for creating or destroying a workspace. For my nightly builds I want to make sure that I start with a fresh workspace each time so I destory and re-create the workspace, but there is no FB action items for this.
Second, the TFS WorkFolder Unmap command only accepts a local path for the parameter, and the action fails if you try to pass it a server path ("$/"). However TF.EXE accepts either a local or server path, so for example this command works fine if I run it from DOS:
TF workfold “/workspace:%WS%” /unmap “$/”
Another issue I have found with FinalBuilder pre-processing my TFS commands:
If I map a TFS folder to a local folder, FB will verify that the local folder exists or the action will fail.
However if I run the exact same command from the command line, it will not throw an error. TFS will aloow you to map to a non-existant local directory. The directory will be created upon first get.
So FinalBuilder forces me to add a Create Directory action before the TFS Map Action that IMO shouldn’t be necessary.
Hi Mike,
We now have a test build with all these issues addressed, and new Create/Delete Workspace actions. It’s all undocumented at the moment, but it’s there if you’d like to check it out.
https://www.finalbuilder.com/downloads/finalbuilder/500/FB500_80.exe
(The build is uploading now, it will be online in about 20 minutes.)
The only issue I noted was fetching files to directories which do not yet exist. The FB TF actions use the working directory to determine the workspace context. You can still Get to a nonexistent (but mapped) directory but you need to set the Working Directory to the parent directory and specify the subdirectory as the directory to Get.
- Angus
OK, I’ll have a look. For now I’ve worked around the issues I stated.
Here’s another thing regarding TFS:
When selecting a revision of source to GET with the TF Get Action, it wants me to select a specific version via drop-down box. I supposed that this is fine is you are always getting the same version type (eg always getting from a label, or always getting from a date, etc) but if I already have my VersionSpec in a variable, there is no way to pass it directly to the TF Get Action. I would have to do some parsing and then wrap it up in a big messy flow control structure.
Could you add an option in that drop-down to allow me to just pass my variable directly to the VersionSpec of the TF command?