1. Home
  2. Build Automation Tools
  3. Jenkins Reviews
  4. User Review of Jenkins
Let your workforce interact by keeping them on same page!
March 28, 2019

Let your workforce interact by keeping them on same page!

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

Overall Satisfaction with Jenkins

We use this technology throughout the company. Most of the time we integrate this with Git. Just by installing a Git plugin to the dashboard we are ready to rock and automate. We do the following process (this step by step guide will brief you more on our work): 1. Install and Integrate Git plugin with the dashboard of Jenkins (localhost:8080), 2. provide the URL/repository URL, 3. git pulls request so as to sync save all data to Jenkin workspace, 4. go to SCM, and select Git in freestyle project, 5. execute the operations and some batch commands, and 6. you are done! Now you are ready to automate your tests (Plugin wise) and debugging. We mostly use mailer application which triggers a mail to all the recipients when our production code builds successfully.



  • Real-time deployment and synchronization.
  • Automated Test cases and debugging.
  • We really like the tool/plugin called Mailer.
  • Best for DevOps. Reduced builds and processing time.
  • Once we organized a hackathon with our GitHub Storage. Jenkins was integrated at that time. We had a 20GB plan, but it oversized to 50GB. We had to bear a large sum of money which was unpredicted by our company. Being a startup we cannot bear such mistakes.
  • Jenkins cannot be easily studied and managed. We have to recruit personnel part-time for managing and servicing the server.
  • Though it is open source, there is no dedicated community driven forum or support. There are 3rd party discussion and support portals. Thus, we use Gitter always for debugging and solutions.
  • We mostly rely on freelancers all over the world which understand our problem statement and start to work on immediately because of Jenkins. This keeps the production safe and lets the work to carry on in another environment.
  • Integration to GitHub helped a lot to sync our older releases of the projects. Better updates were given to the customers. The "GitHub issues" plugin is a savior for updates and patches.
  • Most of our Ubuntu servers were ready to cope up with the technology rather than the windows systems. Thus we migrated to Ubuntu systems all over the workforce. Easy installation on Ubuntu helped in delivering the release at the right time.
No, when we integrated this with GitHub, it becomes more easy and smart to manage and control our workforce. Our distributed workforce is now streamlined to a single bucket. All of our codes and production outputs are now automatically synced with all the workers. There are many cases when our in-house team makes changes in the release, our remote workers make another release with other environment variables. So it is better to get all of the work in control.
Jenkins is open source, thus has a large number of plugins rolled out already. All major VCS, SCM, Git, and Maven applications support Jenkins. They even support Docker which is trending in DevOps nowadays. It has more than 50 APIs and plugins to work on. Thus, it is always appropriate to have Jenkins when you have a distributed workforce and to sync with everyone. To avoid synchronization problems in the distributed workforce and development, we use Jenkins. Code pushed to VCS can be built over another system so as to deploy in the production/release.