Jenkins helps automate your teams efficiency!
May 22, 2023

Jenkins helps automate your teams efficiency!

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

Overall Satisfaction with Jenkins

My team primarily uses Jenkins, an application deployment tool. We create automated jobs that test code and then deploy to servers/containers and restart the apps. We have also begun implementing several CI/CD uses where we are able to automate jobs to deploy container infrastructure code to Git and have runners automatically deploy into our environments.
  • Works with Git very well.
  • Easy to write in preferred coding language.
  • Easy to allow varied levels of access to different jobs/dirs.
  • Large selection of plugins to customize.
  • Jenkins config.yaml recovery is not smooth and takes a lot of legwork.
  • Plugins that go out of date can cause issues with upgrades.
  • Progress UI frequently lacks detailed descriptions from Jenkin's side.
  • CI/CD
  • Git Integration.
  • Automated/Scheduled Jobs.
  • Access Control.
  • Improves Engineer to Dev efficiency.
  • Maintains consistency between users.
  • Provides project visibility.
Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used (TravisCI/GitLab/Azure) provide other options but can obfuscate the process due to the lack of straightforward simplicity. In other areas (capability, power, customization), Jenkins keeps up with the competition and, in some areas, like customization, exceeds others.

Do you think Jenkins delivers good value for the price?

Yes

Are you happy with Jenkins's feature set?

Yes

Did Jenkins live up to sales and marketing promises?

Yes

Did implementation of Jenkins go as expected?

Yes

Would you buy Jenkins again?

Yes

One scenario we use Jenkins regularly is with a scheduled Jenkins job (akin to a cron job) that runs every morning and takes inventory of all VMs/Containers/Servers. This inventory monitors changes in average resource usage, and services that are up or down, and backs up logs for troubleshooting. This job requires no attention, and Jenkins manages it all automatically. Another scenario in which Jenkins was utilized less effectively was in an attempt to actually manage virtual machines (spin up/spin down/reallocate) in vSphere. While we eventually got it to work, Jenkins had a hard time interpreting some of the logic we provided it. Admittedly, Jenkins may have a plugin to assist with this need, we simply found it tedious and decided to go another route in the long run