Jenkins Reviews

We use Jenkins for integrated reporting. We have different projects that require coaching, gate configuration, and clone effects. We build packages, deploy, and upload-pack eights. We start at software changes and follow the process through to final testing and eventually launching. 

Jenkins has excellent task planning features. 

We have a variety of examples in our organization.  We have security configurations that we would like to isolate across our platform. It is not always easy to control the permissions for each user. There are cases where I do not want everyone to have access to the technical aspect of a job or even that the job exists.

I have been using Jenkins now for ten years.

We have found Jenkins to be very stable.

I believe Jenkins is scalable. We have over two hundred users. We have plans to increase this number.

We have not used technical support. We just Google, from the internet. Most of the time we can solve it on our side.

The initial set-up is easy for a single-link system. For more complicated systems it is not easy. As a product, Jenkins has been in the top five for more than five years, so that is not a problem.  

We did an in-house implementation. We have an incremental process for deployment. We also have a complete patent for official patent deployment. We have two patents, one for development and one for official relief. We have an integration team that is responsible for these patents.

Jenkins has a free licensing program.

Jenkins is the most popular automation engine in the world. There are other options, but fewer users. There are some other choices in the market but Jenkins is definitely number one. I would rate Jenkins an eight out of ten.

We use Jenkins for management purposes.

The most valuable features of Jenkins are creating builds, and connecting them with Sonar for Sonar analysis. Additionally, we connect it with other vulnerability tools, such as WhiteSource which is useful.

Jenkins could improve the integration with other platforms.

I have been using Jenkins for approximately two years.

Jenkins is stable.

I have found Jenkins to be scalable.

We have different teams within our company using this solution with different types of setups. We have approximately 25 users using the solution.

I have not contacted the support from Jenkins.

The initial implementation of Jenkins is simple.

The installation of Jenkins is done by our team.

I would recommend this solution to others.

I rate Jenkins an eight out of ten.

My primary use case is as a CI pipeline in order to deploy onto the GCP. This allows us to push any changes into the master brand.

The major benefit of using Jenkins is that it's a very secure way of deploying something to the cloud. It has also improved the drawbacks of manual deployments by making them more robust and secure, and it helps the user avoid mistakes because all the checks are there in one script which can be used every time.

The most valuable feature of Jenkins is the logs it provides - these are very helpful in understanding error conditions so we can see where the problem lies and go in and check it. Another useful feature is the GUI, which estimates how long a particular model will need to be executed. It's also very easy to understand for newcomers. 

One area for improvement would be the UI, which currently looks quite outdated and requires the user to go through too many steps. In the next release, I would like to have the ability to use the command prompt to navigate between repositories and to enable features.

There are some minor bugs with this solution, but overall the stability is ok.

Jenkins is very scalable.

The initial deployment is easy if you are familiar with script creation - a person who is unfamiliar with this might have difficulties with setup. It can be set up by a single person in four to five hours.

I would rate this solution as eight out of ten.

The Jenkins Job DSL plug-in is the most valuable.

We have been able to create CI jobs for each branch of our repository. Being able to test builds for each branch before it is merged to mainstream branch helped to improve stability of the app and have faster develop-test iterations.

The installation process could be simplified, especially on Mac OS X.

I've used it for eight months.

Yes because the installation process is not obvious.

The default settings do not work properly on Mac OS X. You have to tweak JVM parameters and allocate more heap memory as well as change other parameters to have a stable Jenkins server.

I haven't had to scale up yet. We have one build box which is running two agents on it.

As this is open source, there is no such thing as customer service, but there is a big community to look for information and get answers.

As this is open source, there is no such thing as tech support, but there is a big community to look for information and get answers.

Personally, I previously used Bamboo. I switched because I changed jobs and at my new place Jenkins had been used. It would unjustified to do a move from Jenkins to Bamboo, given that Jenkins is capable of performing same tasks.

It was complex and additional knowledge about launch agents and daemons is required. There are at least three, if not four, different ways to install and configure Jenkins, which is not always good.

We implemented it in-house.

It's high because the product is free.

The original setup. for us, was the cost of a new Mac Mini box which costs, from $1,000 to $2,000 depending on the configuration.

This is a very good, powerful and flexible product, but requires a lot of time investment to get the maximum out of it.

Jenkins has good plugins and a secure platform.

I have to take the source code, build it, and test it with SonarQube. After passing it, I make the container, and with this container, we deploy to Kubernetes.

Even though you can get into the public cloud, they have to improve the base layer on marketplaces.  

I have been using Jenkins for the past three years.

Jenkins is as stable as the public cloud. 

You have to manually scale Jenkins.

The setup of Jenkins takes a lot of time. Having faster deployment would be helpful.

The time has come for companies to move to containers. I believe that Kubernetes services are based on the customer's needs in a secure manner. People will go with AWS or GCP.

I would rate Jenkins an eight on a scale of one to ten.

We use Jenkins for building our applications, deploying our applications, and some automation tasks.

We are using the open-source version and there is a lot of plugins and features that are available and it works on agents for free. In other solutions, it will cost extra to use them with the agent.

The UI of Jenkins could improve.

I have been using Jenkins for approximately six years.

Jenkins is stable. It provides all the required features for stability, such as backups.

Jenkins is scalable because it is open source and it integrates with other third-party vendor tools which are currently in the market, such as Microsoft Azure or Amazon AWS. It gets very well integrated with all the new tools, it doesn't remain isolated.

We have multiple projects that are using this solution and each project has multiple users. In one project we could have 50 users or in another 10 users are using it.

We didn't face any issues to escalate to Jenkins for technical help.

We have previously used Bamboo. I use both Jenkins and Bamboo per our project requirements. Jenkins is more suitable for commercial projects and is more scalable and flexible as compared to other tools because its core focus is on integrating and updating automatically.

The initial setup of Jenkins was straightforward. It's very lightweight and it only requires Java on your system as a requirement.

We did the implementation of the solution ourselves with our team.

We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source.

My advice to others is to explore Jenkins well and it is integrated with the scripting site. Teams should explore the scripting part of the Jenkins because everybody's nowadays is writing pipeline as a code for automating their operations. They should try to utilize the new feature provided to them, such as pipeline as a code. 

It does not matter what solution they are using, such as Microsoft Azure DevOps or Amazon AWS DevOps, Jenkins will integrate with other solutions. They should try and use Jenkins even if they're using some other tool.

I rate Jenkins an eight out of ten.

When have to execute continuous testing with schedules and after test, if we want to run additional validation and verification we use Jenkins. 

Jenkin can do additional validation of our test executions of the results and collects data points.

The most valuable features of Jenkins are its ease of use and good plugins available. You are able to connect to a lot of solutions.

Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere.

I have been using Jenkins for approximately two years.

The stability of Jenkins has been good in my usage.

Jenkins has been scalable.

I have not needed to contact the support.

I have previously used Bamboo, but it is a smaller solution than Jenkins.

The initial setup of Jenkins is straightforward. The process took a couple of minutes.

We are using the freeware version of Jenkins.

I recommend Jenkins to others.

I rate Jenkins a nine out of ten.

We used it for continuous integration and had its latest version in the previous organization. I am now using Azure DevOps.

It is open source, flexible, scalable, and easy to use. It is easy to maintain for the administrator. It is a continuous integration tool, and its enterprise version is quite mature.

It has good integrations and plug-ins. Azure DevOps can also be integrated with Jenkins.

Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins.

I used this solution for around one and a half years.

It is scalable. We had five users of this solution.

We were using another solution from Automic.

It is easy and quick to install. It took us less than an hour.

I installed it. You just need a single resource for its deployment and maintenance.

There is no cost. It is open source.

I would recommend this solution. It is good for small companies but not for big companies. It has a good interface and was easy to customize. We were also using another plug-in to enhance the user interface.

I would rate Jenkins a seven out of ten.