We use Travis CI for our github-hosted open source game project, and for our website deployment.
Whn I worked at IMVU, we ran a heavily modified buildbot for continuous deployment. In later jobs, I've seen Jenkins used, but did not like it. There was a tendency for tests to take several minutes, which wasn't so much Jenkins' fault, but a result of developers not running tests on their own machines.
As far as advice goes: I don't think the tools are as important as it is to empower developers to run all tests on their own machines. When some step breaks on the build server, how are you going to debug what happened? For that reason also, prefer unit tests and dependency injection over complex integration tests whenever possible.
Log in to continue
We're a place where coders share, stay up-to-date and grow their careers.
We use Travis CI for our github-hosted open source game project, and for our website deployment.
Whn I worked at IMVU, we ran a heavily modified buildbot for continuous deployment. In later jobs, I've seen Jenkins used, but did not like it. There was a tendency for tests to take several minutes, which wasn't so much Jenkins' fault, but a result of developers not running tests on their own machines.
As far as advice goes: I don't think the tools are as important as it is to empower developers to run all tests on their own machines. When some step breaks on the build server, how are you going to debug what happened? For that reason also, prefer unit tests and dependency injection over complex integration tests whenever possible.