TeamCity and Git? MKS?

We've been trying out TeamCity and we love it.  Unfortunately, we are slated to move very soon to Git.  So...
1. Has anyone tried to use TeamCity with Git's cvs emulation?
2. Any plans for an official JetBrinas Git plugin to TeamCity?
3. Anyone with experience in building TeamCity VCS plugins?  Is it a major effort, or relatively easy?  Is the SPI similiar to IDEA's VCS plugin SPI, so that we could maybe use git4idea as a starting point?

The same actually applies to MKS.  Several other teams in our company got a look at our TeamCity site, and are all asking lots of questions, but they are all using MKS Source Integrity, so we have the same issue there.

6 comments
Comment actions Permalink

Git support is in progress, we hope to include it into the upcoming 4.1 release. I think working version of this plugin will be available in the subsequent EAP builds (however the first 4.1 EAP build which we plan to release soon won't include Git).

MKS support can be written as plugin. Moreover there are open source VCS plugins which can be used as a reference:
http://www.jetbrains.net/confluence/display/TW/AccuRev
http://www.jetbrains.net/confluence/display/TW/Mercurial
http://svn.jetbrains.org/teamcity/plugins/clearcase-vcs/

Also some details on VCS plugin implementation can be found in our documentation:
http://www.jetbrains.net/confluence/display/TCD4/Extending+TeamCity

0
Comment actions Permalink

To supplement Pavel's answer, here are the links to the issues filed in our tracker:
Git, MKS.

Feel free to watch/vote for them.

0
Comment actions Permalink

Thanks guys!  Sounds good.  I will be having someone take a look at the SPI's, but do you guys know offhand how similiar it is to IDEA's VCS SPI?  Are they completely different, or do they share some?  There's an open source MKS plugin for IDEA that would be a great starting point for a TeamCity plugin if there is any similarity between the SPIs.

0
Comment actions Permalink

The difference is significant. VCS plugin in TeamCity needs to be able to build patches in TeamCity format to be sent to an agent. There is no such functionality in the IntelliJ IDEA VCS plugins. Also in IntelliJ IDEA you do not need to collect changes between revisions, but in TeamCity this functionality is a must.

Of course code reuse in the implementation is possible, but API is different.

0
Comment actions Permalink

Makes sense.  Sort of a shame, but I see the reasons.  I imagine there is still a significant amount of reusable work in the implementation anyway, as you say.

0
Comment actions Permalink

Hi

I'm the current maintainer of the IDEA mks plugin, and I was interested in trying out TeamCity on our own projects too.

However, after reading Jetbrains Howto/adice for VCS plugins (http://www.jetbrains.net/confluence/display/TCD4/Version+Control+System+Plugin), I'm not sure it's going to be a trivial task at all. Not because of TeamCity SPI, but because of MKS limitations.

AFAIK, the concept of "project wide revisions" doesn't exist in mks (not even in the ability of checking out a project as it was at a particular date like you can in cvs). The only case where you can do it is on a project's checkpoint.

So if anyone finds a way to do it I'm very interested

0

Please sign in to leave a comment.