I have upgraded version control from StarTeam 2009 to the StarTeam 13.0 in order to support my Windows 7 x64 installation. The FinalBuilder StarTeam actions I use are failing - it appears due to a couple of command line flags that are no longer supported ( -x, -stop).
For example, the FB "ST Check In" action generates the following command line, which fails:
stcmd ci -is -filter "MGU" -p "user:*****@Hostname:49201/Project/View/" -x -stop "*"
If I edit that command line by removing the -x and -stop parameters and then run it manually, the command completes successfully. The same approach works with the "ST Create Label" command line.
Is there any chance the StarTeam actions would be updated to support the new release of StarTeam? I realize that I can probably use an "Execute Program" or "Shell Execute" action to accomplish this - it would just be less convenient and more difficult to maintain.
I did some more investigating, and it looks like I should be able to use the “ST Generic” action for the functions I need as long as I select “do not add server/username/password/etc” and instead include those details in the connection string in the command line. The main downside is that the password is displayed in plain text in the log file.
It looks like the next version of the StarTeam SDK will silently ignore the -x and -stop switches rather than generating an error, which should resolve this issue. Note that the last version of the SDK that supported these switches was 2009 (Ver 11.0).
Apologies for the delay in replying. The starteam actions all have an extra script event, OnGenerateStarteamOptions, which gives you access to the internal commandline builder object. Select the action in the actionlist, switch the script editor and in the OnGenerateStarteamOptions tab, set the language to javascript and add this code :
I don’t have a working Starteam install to test this here, my trial ran out some time ago and my requests for a free license have gone unanswered (we can’t possibly purchase every product we integrate with, most vendors are happy to provide us with a license).
Hmm… doesn’t work for me either, that’s because RemoveArgument takes and argument object not a string. There is a RemoveArgument2 method that does take a string though, so that’s what you should probably use. I have added a RemoveArgumentByName method for the next update.
I suspect you will need to keep the javascript, they removed the arguments we were using with older versions of starteam, I doubt they would have added them back. Imho they should have just had their usage print out a warning message rather than fail. Some developers just don’t get backwards compatibility.
I upgraded my StarTeam client to 13.0.1-30 today (which is the client associated with Starteam 2014, looks like they only released the server) and re-ran without the RemoveArgument2 feature. The checkout works as expected now.
They apparently fixed it so that the client does not reject the -x and -stop parameters:
Running StarTeam with command line : co -o -p “myusername:******@starteam.xxxx.com:49201/XXX Build/XXX Build/” -x -stop “XXX Build.ini” Name,Description XXX Build.ini,Initial creation. 1 row returned. Command completed successfully in 1433 ms.
