Standalone git hooks or Jenkins?

Question

I am trying to come up with the best solution for CI for a group of about 10 developers when it comes to testing a web interface. All I need is for a test suite to run when any of the devs push their code. I don't need to worry about building/compiling or deployment because we have other teams for that. I have considered Jenkins, but have read it can be tedious to set up, requires maintenance and takes up a lot of disk space. In my situation using Jenkins seems like an unnecessary amount of work and just using Git hooks might be better, but I have also read using Git hooks alone for CI is bad practice. Would one of these be the best solution, or is there something else I have not considered?

Answer 1

Jenkins is a deployment system which can run defined tasks and tests on your code and build that code for your production systems. If some of that tests fail it stops building. The installation of Jenkins is very easy.

So testing is normally a step in the deployment process. You should run the tests before your changes go live to prevent errors.

I don't know if it's a good idea to run your complete tests on every push. If you have some tests that have a long running time it can cause errors if a lot of people push your changes.

In your case i would prefer a code review system like Gerrit or the build in systems in Github or Bitbucket. Then 2 people have to check the code and can check if there are some errors.