Jenkins Reviews

• Extensibility
• Usability

We've achieved continuous integration and delivery on all our commits, securing the quality of all of our products on their main branches. The features used come almost out of the box.

Many of the plugins needs to be streamlined, their terminology needs to be the same and some plugins should be split into multiple smaller plugins.

Since 2010, so almost five years.

No issues encountered.

Minor, but those issues typically gets fixed after reporting them. Some issues can be addressed as pull requests, fixing them myself.

No, not after the lazy-load of items were introduced.

5/10.

5/10.

I used Hudson before, so the switch was quite natural.

In-house implementation.

My colleagues and I did the setup, so only the hours we spent doing it.

We also looked at Buildbot.

Just go for it. It's simple and intuitive.

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.

It's more structured, using naming conventions.

• Customization
• Automation

It's very useful when you want to automate different processes from beginning to end.

Maybe centralized user management. (We are not using all the functionalities of the product).

I would say it's a quite stable system.

As I mentioned, we are not using all the feature of it, so it's very easy to scale it.

It's free software with a big community behind it, which is very good.

No previous solution.

It's pretty straightforward. Use apt-get to install Jenkins, and then there is just some minor configuration work.

Some of the add-ons are too expensive.

No. When I started, Jenkins was broadly used.

Start with Jenkins as your first CI solution.

• Continuous build and testing
• Distributed execution of build and test jobs

It is essential for software development and team collaboration. Without this tool, we would be helpless.

Immediate feedback on build errors, regression.

Pipelines are still young and promising. But this part still has some room for improvement.

The documentation on plugin development could be better: more examples. 

Sometimes, out-of-memory problems, but lately this has not occurred often. Sometimes there are obscure Java errors which are hard to understand.

No issues.

If there is a problem, I usually find the solution in the community. It is a large community and that helps a lot. Also, there are very valuable conferences.

I used CruiseControl but this died.

Very easy setup which has even improved over the years. Now I use Docker. Installation of plugins is also very easy.

It is a free product.

BuildBot and CruiseControl.

Don't forget to look into the plugins. It's not only Jenkins but also the plugins which make it a very valuable product.

In this solution, you can write scripts and put job parameters in them with time and dates when to activate. We can create a web book that is automatically configured. The automated elements are easy to use and you can put them into your server. Additionally, there are plenty of plugins available. You can use the plugins to push your code into a target or container. There are many features available in this solution.

The scriptwriting process could be improved in this solution in the future.

I have been using the solution for one and a half years.

The solution is stable.

We have not had any issues with scaling the solution.

I have previously used Bamboo and it is really easy to use, user-friendly, and the UI well designed. The control output of Bamboo is highly interactive for the user. 

I have also previously used Sonar but it is a lot different than this solution and Bamboo.

The solution is one of the lowest costs compared to competitors.

When selecting a solution I would advise checking their budget, the volume size they are performing, and what full-stack they are performing on. Based on this information, they can better determine what solution is best for them. If they have a low budget this solution would be great for them. 

I rate Jenkins an eight out of ten.

• Scalability
• Controllability
• Organization of jobs

Potential deployment problems pop up almost instantly during the development process. The developers are more confident about their committed code.

They need more useful tutorials about how to write database related plugins. It also needs a "run only" option without option for changing job configuration.

I've used it for six months.

There were some issues with deployment.

There were some issues with stability.

There were some issues with scalability.

No other solution was used previously.

It wasn't complex.

We did it in-house.

It's infinity as the developer's happiness are endless.

It's free.

We did not do a deep evaluation but we did look at Bamboo.

Stay calm and mind the gap between your QA automation team and developers.

This solution is the primary component for our automatic release process, including code smell, integration, and deployment.

This solution has provided us with better quality and less time to market for our software products. We can also automate many procedures like code review, testing, and deployment.

There are a large number of plugins available for integration with third party systems.

The user interface could be updated a little. I think that a REST API is needed to expand the integration capabilities.