The StarTeam actions don’t handle multiple filespecs correctly.
If I type Exe1.exe Exe2.exe then it should, for example, check in both files. But FinalBuilder double-quotes the entire string, like this:
"Exe1.exe Exe2.exe"
…instead of the correct format:
"Exe1.exe" "Exe2.exe"
From the StarTeam docs:
If you use a set of file patterns, each pattern should be enclosed in its own set of quotation marks. For example, you can use ".bat" ".c", but you cannot use "*.bat *.c".
A kludgy workaround, which I hate myself for using, but which works, is to enter this in the action configuration:
Exe1.exe" "Exe2.exe
Note no quotes at beginning or end!
Also, I wish bulk checkout was supported. It’s, well, ideal for builds!
This is not actually documented (I’ll try and get that fixed ASAP), but if you separate the files with semicolons (ie Exe1.exe;Exe2.exe) then you can specify multiple files.
Thanks; I agree that documentation would fix the problem, as I did actually read the docs before asking.
Any idea on supporting bulk checkout? Ideally, the checkout action would have a “use bulk checkout” option which defaults to true on StarTeam 2005 R2 and higher (older versions didn’t have bco).
Do you have any info on this option, or can you point us to any publicly available info on this option (and in which release was it added?). We have given up trying to get a copy of Starteam 2005 from borland, even as borland technology partners (and with an eval copy of FinalBuilder on a cd included with the starteam) we have not been able to get any response from them. My guess is it willbe even more difficult now that the have spun the devtools company out as codegear.
The command you want is bco.bat. The command-line syntax is almost identical to the checkout syntax. bco works mostly like checkout except that (1) it doesn’t report each filename checked out and (2) it’s about three times faster for large filesets. Using bco (with the command-line action instead of the StarTeam checkout action) knocked about a minute off of a six-minute build for us.
ST 2005 R2 is the first with bco. But in that version it doesn’t set the error level on exit; you only know if it failed by reading the output. ST 2006’s bco.exe sets the error level, but I’m not sure the values are documented.
Send me an email and I’ll see if I can get anyone from the StarTeam group to get you a non-trial copy. Most of my “Borland” contacts have gone to CodeGear, but I’ll see what I can do. I might be able to find a “friend of a friend” who can help out.
I’d also be happy to test the action or help you with syntax.
I'm running StarTeam 2008 and would LOVE to have the BCO action. I currently use a FB DOS command action and run BCO from it, but I expose the password to all who view the build status.
