1. Home
  2. Build Automation Tools
  3. Jenkins Reviews
  4. User Review of Jenkins
Most extensible CI tool we've seen
April 18, 2017

Most extensible CI tool we've seen

Josh Quint | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Jenkins

We use Jenkins to coordinate internal infrastructure teams with external development teams to make sure deployments are done in a consistent and automated fashion. This increases security in the infrastructure as well, as we do not need to create user accounts for the developer teams in the deployment environments. We use Jenkins to deploy PHP, Ruby, and .NET applications.
  • Build and deployment automation. You can build almost any code base from most standard code repositories and push the artifacts to the application servers.
  • MANY MANY plugins. The Plugin community is huge, so if Jenkins doesn't do something out of the box, there is probably a plugin to do it.
  • Multiple step orchestration. Any build can be created with many steps, including pre and post build. Additionally, you can tie builds together.
  • User management is a bit simple, and it is hard to manage users across multiple clients with the Jenkins internal database.
  • Automated deployment and configuration of Jenkins itself. The config files are hard to template out and change with each version.
  • Windows Slaves. Windows Java slaves are unreliable, especially when run as a service.
  • It's open source, so the cost is very good.
  • Allows for streamlining deployment process, saves dev team a lot of time!
  • Simplified user management on application nodes.
Jenkins does a much better job of working with interpreted languages, and has a much larger plugin base.
It's very well suited to deployments of interpreted languages, many other CI tools don't work with that type of deployment well. Linux Slave plugins work VERY well. Could use better support for user management, and multiple node deployments. Plugins are extensive, but there is a bit of steep learning curve when setting up Jenkins for the first time.