Jenkins Reviews

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.

- Run automated tests with release pipeline.

- Run tests against different environment.

- Manage selenium grid.

- Integrate with slack, browserstack and AWS.

CI tools such Jenkins and TeamCity, totally helps our release and tests. It saves our money, time and labour cost. And make release/delivery of the our product more visible. It drives the development team and other departments’s ambition.

Jenkins: pipeline/delivery pipeline and we can use shell script in the configuration. Jenkins has a lot of plugins.

TeamCity: We can run automaton tests.

For Jenkins: It needs to have less bugs. I do not how they test the plugins, but sometimes, the plugins have issues. I have no time to check where to report the issue.

For TeamCity: It need to be cheaper.

For automation tests, Jenkins nodes some times experience instability. I have no better solution yet, since I have concerns with the networking and firewall as well.

I do not know if it is scalability problem or not. In one Jenkins instance, we had many jobs and we created so many views, it is not easy to find them.

Customer Service:

I have never used them.

Technical Support:

I have never used them.

I prefer to use Jenkins more, because I have used it for a long time and am familiar with it. To me, TeamCity is OK too, but it is not free as Jenkins is. We need to consider the budget, so Jenkins finally won our development’s heart.

I experienced the development switch from TeamCity to Jenkins, and I do not know the exact reason. My current company switched from Jenkins to circleCI.

When I moved automation tests from TeamCity to Jenkins, I did not experience any difficulties, but I have learning curve for circleCI.

We use AWS codepipeline + jenkins.

Before using jenkins + AWS, we used CircleCI.

We use the Groovy language to maintain the Jenkins job configurations which is very convenient. I do not know if we can do that to team city or not, I have not had a chance to try yet. I love Jenkins more without considering budget and the technology trend.

1. CD/CI pipeline
2. Different types of jobs, such as Pipeline, Build, Freestyle, Maven, etc.
3. DSL: Groovy for complicated pipeline flow.
4. Tons of plugins
5. Is able to integrate with other systems.
6. Free
7. Easy to use Jenkins Docker.

It improves our release. It makes the release faster by adding an automated deploy and automation tests.

The bug fix speed is very slow.

More than six years.

Some plugins have critical bugs and are not able to be used.

Most of time, Jenkins is works well. But when you scale up, you need an administrator to manage Jenkins.

You need an internal admin for Jenkins.

CircleCI and TeamCity. CircleCI is not strong at release pipelines. TeamCity is not free.

I feel it is pretty easy to set up Docker in my local computer. 

I do not have experience installing Jenkins on the company-wide used server yet, because I am not an Ops/Admin. I am a user of Jenkins.

Yes. CircleCI and TeamCity.

It meets most of my requirements, such as CI/CD pipeline and an automated test execution. Even if there are some issues in Jenkins and its plugins, Jenkins provides the workaround ability to us. Other CI/CD system are not flexible like Jenkins yet. Also Jenkins provides an API, which you can integrate easily into your application.

When you have more jobs in Jenkins, find an admin to manage the user, queues, jobs, slaves, etc.

I highly recommend Jenkins. It is my favourite CI/CD system.

Jenkins is part of our test infrastructure. We organize the test execution mainly of our performance tests, based on JMeter.

Second, the deployment of release candidates in our test infrastructure is managed using Jenkins.

In the future, we want to use Jenkins more in the field of continuous integration and continuous deployment.

For test automation, Jenkins seems to be our main and central solution at the moment. We want to extend this in the future towards Jenkins pipelines, which can be very useful for having a more dynamic test infrastructure.

Currently, using Jenkins for automatic testing is the most valuable feature for us.

It is very useful for us to be able to collect and manage automatic processing pipelines.

We have issues with the following points:

• The usability and user interface could be improved.
• Clearer feedback for problems and errors would be useful.
  
• The learning curve is quite steep at the moment.
• Our security policy does not allow normal users to introduce additional modules. A simpler way of extending the basic functionality would be nice.

When there is enough disk space and RAM, the solution is stable.

Scalability is not an issue for us.

There is a large open source community where you can find a lot of workarounds and solutions when you have a problem.

We did not use another solution previously.

The setup is straightforward.

Our in-house SysOps team managed to install Jenkins.

Jenkins is open source and free.

We also evaluated Bamboo but decided to go with Jenkins because it is open source and free.

We recommend having the proper infrastructure, and to ensure the maintenance of the server is performed.

• 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.