Jenkins is a good tool to begin an automation
March 29, 2016

Jenkins is a good tool to begin an automation

Anton Fisher | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Jenkins

I use Jenkins for a continuous integration during software development. Jenkins runs builds, tests, code quality tools. Jenkins is configured to run nightly builds automatically and run tests after each change in products. It allows us to react on troubles as fast as possible.

Pros

  • Open source solution
  • Flexible configuration
  • A lot of plugins available

Cons

  • Poor user interface
  • As an open source project it does not require investment to try it
  • As an open source project it has a big community, a lot of people work with it and have a chance to try it
  • As an open source project it allows you to modify and customize it as you want
I have experience with TeamCity. It looks pretty good after Jenkins, the user interface is friendly and modern. The functionality is similar to Jenkins. It is not a big problem to migrate configuration from Jenkins to TeamCity or to return back. You need licenses to use it in serious projects with bunch of tasks, but you get enterprise support.
Jenkins is well suited for:
* Continuous Integration for improving code quality
* Monitoring builds health, code quality "on a fly"
* Integration to other monitoring products via rich Jenkins API
* Run builds and tests in different environments
* Organize build tasks, dependencies, sequence of tasks
* Fire notification to whole team or team member directly about troubles
* Easy manage credentials for Git, ssh hosts, etc
* Install build-agents automaticaly, easy to add new one.
Open source project which gets updates constantly.
Also Jenkins is well translated to other languages.

Comments

More Reviews of Jenkins