1. Home
  2. Build Automation Tools
  3. Jenkins Reviews
  4. User Review of Jenkins
Just a user of Jenkins
March 30, 2017

Just a user of Jenkins

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

Overall Satisfaction with Jenkins

Jenkins was used by the development team to automate a deployment method for the customer. As such, Jenkins was a great asset working in conjunction with Git in order to provide a certain level of CM. Jenkins provided the much-needed build process that takes the guesswork out of making sure each build was done properly.
  • Automated Builds to help rule out human build fails. Indicators that also notifies if a build has failed.
  • Documents changes to each file in the build as well as keeping a log of the builds over time in case you have to revert.
  • Works particularly well with Git repositories as the hooks automatically can trigger a new build once it has detected any updates.
  • As a new user that jumped into Jenkins, it seemed a bit more overwhelming to use at first. If there was an intuitive guide that could help out the workflow would be great.
  • It took a little elbow grease to get Jenkins to cooperate with Git.
  • When builds fail, I wish it would give a little bit more detail in troubleshooting what went wrong.
  • From a user point of view, I feel that it makes a huge difference being able to automate the build process worry-free
  • Being able to track the different builds from multiple users helps on any level in pinpointing what might have gone wrong.
  • The only negative impact would be the time to take to understand what jenkins can offer
I have not evaluated any other solutions as I was just a user.
I feel that if the working group knows what they are doing, Jenkins can be a huge asset in which can help drastically reduce build fails because of human errors. The challenge is how Jenkins can fit into your current process as technology like this is only as good as its implementation.