Jenkins Reviews

I can build slaves and extensions through plugins.

Automation in general has been improved.

Provisioning of VMs during deployment.

Five years.

Provisioning VMs during deployment was an issue.

No issues encountered.

No issues encountered.

Not needed.

Not needed.

We previously used Hudson, and CruiseControl.

Initial set-up was straightforward.

We implemented in-house.

We compared Jenkins to CruiseControl.

It works.

We use this solution for continuous integration and deployment, using Groovy Script for pipeline node configuration.

This solution has helped us in automating the build and test process, reducing time.

The most valuable features are plugins that make my server highly available.

The upgrades need improvement.

I use Jenkins for Continous Integration or Continous Deployment to run test case execution in Nightly build atmosphere. Integrating test scripts to Jenkins is easier and it can run based on the frequency mentioned in settings.

Jenkins has helped us in executing our test scripts without the Dev team during night time.  It automatically fetches the latest build or codes and execute all your test scripts and share the report with the respective team and stakeholders.

I have found the following features extremely helpful.

• It is open source & user-friendly.
• It can deploy code instantly & generate test reports. The requirements for continuous integration and continuous deployment can be configured manually.
  
• Integration work is automated.
  
• It can be integrated with other major tools.

They should improve the Version Control tracking system in Jenkins.

Most obvious: Having builds and test tasks triggered on commit helps not to break the product.

From my own experience:

We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity.

Integration with GitLab reduced time used for code reviews. Jenkins posted build state and code quality reports into the merge request.

Simplified build scripts: Organisation started to integrate Pipelines as a part of a build, and built a library of common functions. It simplified and made our build scripts more readable. 

Automation of chores like deployment, frequent manual tasks (like running scripts on test and production systems) reduced the time used and the number of errors made by engineers, freeing them to do meaningful work instead.

• Configuration management: It is so easy to configure a Jenkins instance. Migrate configuration to a new environment just by copying XML files and setting up new nodes.
• Programmable pipelines: In recent versions, Jenkins has a Groovy Sandbox where build scripts execute. I have never seen that powerful a tool in CI solutions yet. On other platforms you can use shell scripts, but Jenkins' solution is much better in terms of readability and portability. And given that you can create your own libraries for the Jenkins Pipelines, it becomes much more powerful and DRYer, simplifying work of DevOps and build engineers.
• Brand new Blue Ocean UI: Jenkins used to have a pretty outdated UI. Now, you can use the Blue Ocean plugin to make it nice, clean, and modern-looking. Also, it has very good integration with Pipelines (basically it is built to use Pipelines).

UI: Jenkins relies on the old version of interface for configuration management.

Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things.

Rarely. I can remember only one time we lost our build info after upgrading Jenkins, somewhere around the 1.6xx versions.

Sometimes you have Jenkins restarting because of OOM errors.

No scalability issues. I used to have up to five worker nodes with one master, and it did not produce any slowdowns. I have never had bigger deployments.

I have never used technical support directly. The community, documentation, issue tracker, are pretty good, though not ideal.

TeamCity - It’s pretty limited in build runners, mostly targeting enterprise tech (Java, MS Stack, mobile apps) and the price is quite high.

Buildkite - An okay solution, but builds are shell scripts in general. It’s hard to maintain them. Also, I had weird issues with SCM integrations and Github.

GitLab CI - It’s coupled with GitLab too tightly. It’s pretty difficult to configure. It’s slow and requires a lot of resources to run.

As for me, I just start to use it. It runs builds, unless you need something more complicated.

Setup of commonly used plugins is very straightforward, but it can be more difficult to get it running with exotic technologies. Still, it’s much easier than with other solutions.

I used the free OSS version all the time. It was enough for all my needs.

I was always choosing between Jenkins, TeamCity, Buildkite, and Bamboo. Most recently, hosted solutions like Codeship and Travis CI added to the list.

For business needs, Jenkins is the most relevant choice because it can be self-hosted, the price is good, it’s robust, and requires almost no effort for maintenance.

For open source projects, Travis CI is standard.

I like it very much, and I'm actively promoting it on my network.

Take your time to get used to the management flows of the application and builds. Jenkins is very powerful when you know how to cook it.

This is our CD solution for Java APIs and Microsites.

This solution automates the deployment process and therefore increases productivity.

The most valuable feature is its ability to connect with different tools and technologies.

This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager).

• Uno-choice parameters
• Publishing HTML reports
• Emails on builds
• Active Directory
• Role Based and Project Based Matrix Authorisation

We work on distribution, and are required to build and test packages frequently. Using Jenkins we have configured (generic) and automated the complete build procedure.

1. There's a plugin Monitoring which have certain issues with some versions of Jenkins
2. Jenkins user login and authorization case-insensitive, eg: if user John is given authorization permission then JOHN, JoHN, johN etc. all should be authorized.
3. Disabling of cancel permissions to some users in Jenkins is still not working, even if we uncheck the cancel permissions. If build permissions are given to that user, cancel permissions are granted automatically
4. Plugin to disable Back button navigation in Jenkins#
5. Uploading multiple files using patch parameter in Jenkins

I've used it for around six months.

No major issues, it was pretty smooth.

With few plusgins, like Monitoring. it crashes.

Not as of now.

No interactoins as of now.

No interactoins as of now.

We upgraded from Hudson which is similar.

It was pretty straightforward.

We took it from Open Source so there was no vendor involvement.

Our company is in development. We provide development solutions for our clients. 

Jenkins is a code repository. We use it for the code repository.

It is easy to use.

It could be cheaper.

I have been using this solution for four or five years.

 It is stable.

It is scalable. Currently, we have around 67 or 70 users. We have plans to increase its usage.

I didn't interact with them. Other people take care of this.

We used GitHub.

It is easy to install.

There were other developers who installed it. For deployment and maintenance, we have a team in which everyone has a role. They do their own thing.

It could be cheaper because there are many solutions available in the market. We are paying yearly.

I would recommend this solution. I would rate Jenkins a seven out of ten.

We use it for build.

It improves our process because it's incorporated with the code. We don't need a UI to design the build process. It's like code for building.

Pipeline.

I think we have everything we need in Jenkins, really we're content with what we have in it. If I had to name something, I'd like to see more on the cloud, cloud integration, like to Amazon and  Google. I'd like to see more plugins for those.