What is your experience with CI server git support (Windows)?

I read the feature description of all kinds of CI servers, but they don’t tell me how good the support is in practice. What is your experience?

  • How to configure a jenkins job to send mail if a SCM commit
  • Jenkins: deploying war files from artifactory
  • Can't su to user jenkins after installing Jenkins
  • Jenkins + Cmake + JIRA = CI of multiple interdependent projects?
  • how to build just svn changed files in jenkins
  • Blocking a jenkins task until all downstream tasks complete?
  • Proper git workflow scheme with multiple developers working on same task
  • SourceTree - remote: Unauthorized
  • With git, how can I perform a git add and still have it ignore the patterns in .gitignore?
  • How to make Git not ask me for password when accessing remote repositories?
  • Using LDAP as auth method to manage git repositories
  • how to keep git submodule on-branch status after cloning superproject?
  • 4 Solutions collect form web for “What is your experience with CI server git support (Windows)?”

    Here’s a matrix of CI server features, including GIT support (scroll down).

    EDIT: wrt. experience, I’ve found Hudson easier to configure and maintain than CruiseControl. I’ve found in the past that:

    1. CruiseControl has suffered from a non-intuitive configuration that requires some repetition of the same XML for different builds
    2. in particular the integration and reporting of JUnit results can consume a lot of memory (and fail) when you have a lot of tests (this is because the JUnit XML reports are translated to HTML via XSLT).
    3. Occasionally it has trashed its state files, or spits its dummy out if it can’t write to a results directory (if it isn’t there), and comes to a halt without useful error messages. Consequently I’ve spent more time than I care diagnosing and fixing troublesome CruiseControl installs.

    Obviously other people will have different experiences, but I’ve seen the above at different client sites.

    I’ve used TeamCity for a few months, and git for over a year. TeamCity was a breeze to set up, and recently added built-in support for git (before that the plugin worked pretty well for me too). Their git module works pretty well, but it gets confused if you switch the git server you’re pointing to after creating the VCS Root. Not much that I can find in terms of logging to figure out what’s going wrong either.

    But it works 95% of the time, and I’m happy with it overall since configuration is so easy.

    My shop’s had a great deal of success with Hudson once we got the configuration worked out (which did take some doing). Is there some specific area that you’re interested in hearing about?

    We’re using BuildBot with git. In general, it works!
    Our build system has hooks for starting a build whenever a commit is made (actually, a push to the origin). Buildbot’s website shows the blame-list for the build etc. In general it works good!

    Also, seeing some of the features that are to-be-merged into git didn’t have great git support, the developers were VERY responsive and helpful in adding that support. Really, a great system simply because it’s pretty easy to affect things.

    Git Baby is a git and github fan, let's start git clone.