Tuesday, November 23, 2010

Continuous Integration

We use TeamCity as a continuous integration server to build different configurations of Unigine engine, tools, SDKs and so on. We also use Trac as an issue tracker. The problem was lack of their native integration, but it's solved: Max wrote a TeamcityIntegration plugin, feel free to use it.

BTW, it takes about 5 minutes to make full rebuild of Unigine (engine+tools, both release and debug) on a Linux build node, while the Windows one (which has more powerful hardware) spends 12+ minutes for the same build type. So ccache rules, we do miss it for Visual Studio.

4 comments:

  1. Yay for TeamCity! We use it at Unity as well.

    ReplyDelete
  2. Yep, TeamCity is a nice solution indeed.

    ReplyDelete
  3. Why not buildbot? (just curious).

    ReplyDelete
  4. We have very little portion of our code written in Python, plus we need to do a lot of other stuff other then build/test: packaging, deploying and so on.

    ReplyDelete