Gentlemen. Anyone who's concerned.

I've started working on StarTeam integration.
So please give me your opinion.

Starting from which version it makes sence to support StarTeam in TeamCity? 6.0? Or maybe earlier?

Evidently, the earlier starting version is, the more effort the support will require. So please be reasonable.
I've heard almost nobody now uses StarTeam prior to 6.0. Is it true for you? Which version are you using?

Thank you

We are using StarTeam 2005 (= 8.0).

We also are using v2005

2005R2 I would not bother with 6.0. Although many people still use it it is pretty much compatible with 2005 API, and if not people shoud upgrade :-)

2006 API seems to be backward compatible with 2005R2 I use 2006API with 2005R2 server. Actually I doctored it to remove any dependencies on native binaries so I can run under 64 bit VM

We are using Starteam Enterprise 5.4,, company wide. The Starteam administrators here have tried to upgrade once but they ran into a difficult problem. They have decided to stay on this old version for now.

Is there any progress or estimated completion date on starteam support? It is the single issue holding up our migration to TeamCity. Can you point us to the documentation and sample code if possible for creating the plugin ourselves for the current version of TeamCity (2.x).
Thanks!

+1.

By the way, if you have difficulties with StarTeam SDK, just drop it and use their command line utility (stcmd.exe) directly. Maven/continuum does so, as far as I know. Also, you'll assure a better compatibility with stcmd instead of SDK jars.

The StarTeam support development was postponed for a while in favour of the Maven runner rework and time estimation for queued builds. But now I'm back to StarTeam and we're going have something to show within a month or so.

http://www.jetbrains.net/confluence/display/TW/Plugin+Development
This is the link to what may be called a documentation but I'm sure you'll find it poor. The API is still unstable by the moment and doesn't seam worth relying on.

Of course you can try to implement your own plugin, but I would suggest to wait until the native Starteam plugin is ready.

I didn't have difficulties with StarTeam SDK so far, so I don't see any reason for replacement. It's convenient enough and provides compatibilty with older server versions. We use StarTeam SDK 2006 (9) and it works fine with StarTeam server 5.2.

If you do see problems here, would you please describe them more specifically?

Thanks Sergey! Great to know you're back on the task. We're looking forward to testing your updates. We can test them at any time just email me or reply to this thread.

I remember there were two things :

1. few years ago "cruise control" supported StarTeam, but we were forced to recomplile "cruise control" in order to get this support. Probably there were some legal aspects : they could not distribute the SDK inside an open source project: a client needed to provide the SDK himself for the compilation.

2. It's sometimes a mess between one or many versions of client, server version, the version of stcmd.exe that is declared in the PATH. In fact with stcmd.exe you get more control of the version you are using.

3. CruiseControl used SDK, Maven 2 uses stcmd.exe. maybe there was a reason to change.. I don"t know. maybe there are some developers discussions in the mailing lists of manven 2..

I just wanted to say there are two options. Logically, the SDK is meant to be integrated into the third-party products and there is nothing wrong if you do so. ;)

thanks

FYI: We use starteam + cruise control without any problems in the current releases. The only thing we install on the build machines is the normal starteam client and I hope TC can work the same way.

Cool!! How can we test this?

The EAP is going to be released today. Details are in the upcoming release notes.
There are a number of known issues (remember - this is an initial incomplete implementation) but basic functionality is implemented.

We're waiting for your feedback!

Guys.

I just want to remind you that we issued EAP with preliminary StarTeam integration some time ago. ;) But we haven't got much of your feedback since StarTeam support has been EAP'ed.

Does this mean it works well enough or you just had no chance to try it?

There are a number of TODOs we're going to complete by the release of 3.0. These are mostly related to usability/tweaking and they can be found at the "Relates" section of this issue. You have an opportunity to expand this list in accordance to your own needs.

Your experience is very important to us, since we don't use StarTeam internally. We cannot test TeamCity in an environment close to the real life of those teams using StarTeam intensively. So it would be very nice if you point us at problems we cannot catch ourselves before the new release.

Thank you :)

BTW: We're using it in the TC 3.0 EAP and bought TC just because you added this feature. It mostly works but we're regularly afflicted by http://www.jetbrains.net/jira/browse/TW-3110

K. More details. We're using 5725 and we still occasionally (albeit much less than we used to) get an exception similar to the one recorded in http://www.jetbrains.net/jira/browse/TW-3110. The test connection succeeds but the actual build will not. The problem seems to come and go. Full exception detail is below:

jetbrains.buildServer.vcs.VcsException: The selected configuration is not valid for the current view. The configuration of a view cannot be changed to a time before the view was created, a time in the future, or to a label that was not created within the view or that is empty. BTW: I'm not upgrading beyond 5725 due to http://www.jetbrains.net/jira/browse/TW-3747 which appears to be in the more recent builds.

at jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport.collectBuildChanges(StarteamSupport.java:8)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectBuildChanges(VcsChangesLoader.java:32)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.loadChanges(VcsChangesLoader.java:30)
at jetbrains.buildServer.vcs.impl.VcsManagerImpl.loadChanges(VcsManagerImpl.java:362)
at jetbrains.buildServer.vcs.impl.VcsManagerImpl.checkForModifications(VcsManagerImpl.java:240)
at jetbrains.buildServer.serverSide.impl.auth.SecuredVcsManager.checkForModifications(SecuredVcsManager.java:8)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$1.run(VcsModificationChecker.java:7)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)

Caused by: The selected configuration is not valid for the current view. The configuration of a view cannot be changed to a time before the view was created, a time in the future, or to a label that was not created within the view or that is empty.

at com.starbase.starteam.ServerException.forError(ServerException.java:78)
at com.starbase.starteam.vts.comm.BinaryCommand.popException(BinaryCommand.java:549)
at com.starbase.starteam.vts.comm.Command.pop(Command.java:443)
at com.starbase.starteam.vts.comm.Command.pop(Command.java:417)
at com.starbase.starteam.vts.comm.BinaryCommand.readInt(BinaryCommand.java:152)
at com.starbase.starteam.Project_Cmd_Open.pop(Project_Cmd_Open.java:55)
at com.starbase.starteam.vts.comm.CommandMacro.executeOnce(CommandMacro.java:109)
at com.starbase.starteam.vts.comm.CommandMacro.execute(CommandMacro.java:65)
at com.starbase.starteam.CmdMacroGlobalServiceCommand.execute(CmdMacroGlobalServiceCommand.java:46)
at com.starbase.starteam.ViewSession.init(ViewSession.java:41)
at com.starbase.starteam.ViewSession.<init>(ViewSession.java:55)
at com.starbase.starteam.Server.getViewSession(Server.java:563)
at com.starbase.starteam.CmdMacroProjectSpecificCommand.<init>(CmdMacroProjectSpecificCommand.java:34)
at com.starbase.starteam.View_Cmd_GetFolders.<init>(View_Cmd_GetFolders.java:36)
at com.starbase.starteam.View_Cmd_GetFolders.execute(View_Cmd_GetFolders.java:27)
at com.starbase.starteam.Folder_Cache.fetchAllIDs(Folder_Cache.java:324)
at com.starbase.starteam.Folder_Cache.refreshItems(Folder_Cache.java:171)
at com.starbase.starteam.View.getRootFolder(View.java:941)
at jetbrains.buildServer.buildTriggers.vcs.starteam.adapt.SnapshotImpl.findFolder(SnapshotImpl.java:33)
at jetbrains.buildServer.buildTriggers.vcs.starteam.adapt.SnapshotImpl.getHierarchy(SnapshotImpl.java:30)
at jetbrains.buildServer.buildTriggers.vcs.starteam.ChangesCollectionUtil.collectChangesForPath(ChangesCollectionUtil.java:11)
at jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport$1.collectBuildChanges(StarteamSupport.java:4)
at jetbrains.buildServer.vcs.VcsSupportUtil.collectBuildChanges(VcsSupportUtil.java:1)
at jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport.collectBuildChanges(StarteamSupport.java:29)
... 12 more
The selected configuration is not valid for the current view. The configuration of a view cannot be changed to a time before the view was created, a time in the future, or to a label that was not created within the view or that is empty.
at com.starbase.starteam.ServerException.forError(ServerException.java:78)
at com.starbase.starteam.vts.comm.BinaryCommand.popException(BinaryCommand.java:549)
at com.starbase.starteam.vts.comm.Command.pop(Command.java:443)
at com.starbase.starteam.vts.comm.Command.pop(Command.java:417)
at com.starbase.starteam.vts.comm.BinaryCommand.readInt(BinaryCommand.java:152)
at com.starbase.starteam.Project_Cmd_Open.pop(Project_Cmd_Open.java:55)
at com.starbase.starteam.vts.comm.CommandMacro.executeOnce(CommandMacro.java:109)
at com.starbase.starteam.vts.comm.CommandMacro.execute(CommandMacro.java:65)
at com.starbase.starteam.CmdMacroGlobalServiceCommand.execute(CmdMacroGlobalServiceCommand.java:46)
at com.starbase.starteam.ViewSession.init(ViewSession.java:41)
at com.starbase.starteam.ViewSession.<init>(ViewSession.java:55)
at com.starbase.starteam.Server.getViewSession(Server.java:563)
at com.starbase.starteam.CmdMacroProjectSpecificCommand.<init>(CmdMacroProjectSpecificCommand.java:34)
at com.starbase.starteam.View_Cmd_GetFolders.<init>(View_Cmd_GetFolders.java:36)
at com.starbase.starteam.View_Cmd_GetFolders.execute(View_Cmd_GetFolders.java:27)
at com.starbase.starteam.Folder_Cache.fetchAllIDs(Folder_Cache.java:324)
at com.starbase.starteam.Folder_Cache.refreshItems(Folder_Cache.java:171)
at com.starbase.starteam.View.getRootFolder(View.java:941)
at jetbrains.buildServer.buildTriggers.vcs.starteam.adapt.SnapshotImpl.findFolder(SnapshotImpl.java:33)
at jetbrains.buildServer.buildTriggers.vcs.starteam.adapt.SnapshotImpl.getHierarchy(SnapshotImpl.java:30)
at jetbrains.buildServer.buildTriggers.vcs.starteam.ChangesCollectionUtil.collectChangesForPath(ChangesCollectionUtil.java:11)
at jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport$1.collectBuildChanges(StarteamSupport.java:4)
at jetbrains.buildServer.vcs.VcsSupportUtil.collectBuildChanges(VcsSupportUtil.java:1)
at jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport.collectBuildChanges(StarteamSupport.java:29)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectBuildChanges(VcsChangesLoader.java:32)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.loadChanges(VcsChangesLoader.java:30)
at jetbrains.buildServer.vcs.impl.VcsManagerImpl.loadChanges(VcsManagerImpl.java:362)
at jetbrains.buildServer.vcs.impl.VcsManagerImpl.checkForModifications(VcsManagerImpl.java:240)
at jetbrains.buildServer.serverSide.impl.auth.SecuredVcsManager.checkForModifications(SecuredVcsManager.java:8)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$1.run(VcsModificationChecker.java:7)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)

Scott,

The TW-3110 exception should be fixed in the next EAP build: 5813, which features improved StarTeam support.
As far as I know TW-3747 should not be critical for the builds, so it seems that upgrade is worth it.
I hope that in next EAP release we will fix TW-3747.

Scott,

BTW, TW-3110 should not appear if your TeamCity server and StarTeam server clocks are synchronized.