Choosing a build server

Question

I plan to set up my own build server. I am the main project of C #, C / C ++ and Java. I would also like my build server to run some external programs / scripts, such as my unit tests, static code analysis and doxygen.

Suggestions?

Answer 1

Use the Hudson Continuous-Integration Software .

Answer 2

We use JetBrains TeamCity . It is easy to configure, user-friendly, has convenient plug-ins for notifications about assembly events, you can install several assembly workers, define any assembly mechanism (.net, java ...), it can display artifacts, it can run automatically, it can execute any custom script builds etc. etc ... and, most importantly, for free (up to 20 configurations).

We looked far and wide and we found that this is the best ...

Answer 3

Equipment: wheels. Quite a few, or a decent SSD. Much of what you do will be based on disk by the compiler. Not to mention getting the latest version (alone), but, for example, the C ++ compiler generates QUITE several intermediate files during the build process. A decent fast subsystem can make a recognizable difference. This is especially not for you, but for some colleagues, sotit can work a lot at the same time.

Well, enough RAM and a modern multi-core processor, not to mention.

Answer 4

I used Trac and Bitten , which worked quite well. I used it for C # and Python projects.

I have it created, created documents and run unit tests. I am currently studying the work of dotCover to cover tests, which should not be too complicated, because a bitten basically allows you to invoke any shell command that you need.

Actually, I usually run the build system on the old (not very fast) system - for me it is not necessarily very fast. I like to have developers behind fast cars; -)