Hacker News new | past | comments | ask | show | jobs | submit login

Why does Travis do for me that Jenkins or Gerrit doesn't?



Hey theatrus,

Travis is similar to Jenkins, but also very different.

For instance:

1. Every build is run in a virtual machine sandbox so other projects tests won't affect yours (eg. files or dbs left over).

2. The full infrastructure is distributed, the web frontend has been decoupled from the workers completely.

3. All push information sent by GitHub is built by default, so no need to tell Travis to build a certain branch.

4. We use web sockets so you can see the results in realtime.

5. Hosted for free for the open source community.

The core goal behind Travis is to make it easy for open source projects to test against different environments (language versions, databases, services, env vars etc.) with the aim to increase code quality for everyone.

So comparing Jenkins and Travis (the service) is a little like comparing apples and oranges, even though they do have a lot in common.

Hope this helps,

Josh


You mean what does Travis do in comparison to Jenkins or Gerrit? Well it runs the tests of your open source projects for free and with ease.

Is there a Jenkins or Gerrit based project that does this for you?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: