1. Home
  2. Build Automation Tools
  3. Jenkins Reviews
  4. User Review of Jenkins
Quick Jenkins review from a new Jenkins user
April 17, 2017

Quick Jenkins review from a new Jenkins user

Anonymous | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User

Overall Satisfaction with Jenkins

Jenkins is currently being used to automatically build releases when a change is detected in the code base.
  • Automatically creates a build and posts to company managed Jenkins page.
  • Provides ability to access several builds and clearly shows successful/unsuccessful builds with time stamps.
  • Ability to tie into other tools such as instant messaging apps/programs to get up-to-date information or broadcasts of when a build has started/completed.
  • Jenkins provides a 'pipeline' where a user can fine tune instructions for Jenkins to execute. This pipeline is hard to use via the browser as it cannot be resized.
  • Ability to know when a build fails so no testing is waisted on an invalid build.
  • Ability to broadcast when a build has completed has allowed QA to start testing as soon as possible.
  • Adding Unit and Regression tests that get automatically ran after a successful build allows QA to build fundamental tests that get frequently executed and can focus on creating/defining new tests during development cycle. This allows more QA tests to be ran with each development cycle.
I have yet to experience another integration tool like Jenkins.
To be fair, I'm still learning about tools to manage build automation and tests. However, Jenkins seems to be well suited to automate several builds a day and run unit and regression tests with each build. Builds that fail any tests are appropriately labeled.