Jenkins Reviews and Ratings

Use Cases and Deployment Scope

Jenkins is used for triggering builds in our company. We have more than 20+ apps which needs to be deployed , and we take help of jenkins to do so. From frontend, to backend to ML team, all uses jenkins for their deployment.

Jenkins helps us speed up our delivery by allowing parallel builds and testing, significantly improving deployment times. Jenkins integrates seamlessly with Git (GitHub/GitLab), Docker, Kubernetes, and other DevOps tools we use, enabling end-to-end automation.

Likelihood to Recommend

1. Suited well for a company which has more than 10 apps to deploy. 2. Not suited for a place where Serverless or Event-Driven CI/CD with Minimal Setup is required.

3. If project requires fine-tuned control over build steps, conditional deployment flows, and script-heavy automation, Jenkins provides unmatched flexibility using Jenkins file and Groovy scripting.

Use Cases and Deployment Scope

Jenkins integrates well with tools like Ansible, Terraform, Docker, and Kubernetes. Used to automate the build, test, and deployment processes across multiple teams, projects, and environments.

Likelihood to Recommend

Centralized pipeline management using shared libraries and templates. Multi-branch pipelines for handling parallel feature development. Send notifications to Slack, Teams, email, or enterprise dashboards. Integrate with SonarQube, JIRA, Prometheus, and others for metrics and tracking.

Produce detailed test and deployment reports—Ross's large dev teams.

Use Cases and Deployment Scope

We are using Jenkins for continuous integration and continuous deployment in our organization. It has helped in moving towards automation and currently major applications created using TIBCO BPM Enterprise, React UI and Node JS are being deployed using Jenkins. Jenkins has helped a great deal to not just developers but system administrators as well. Any additional tasks which need to be completed along with deployment are added in the scripts which gets executed during deployment.

Likelihood to Recommend

Jenkins is suitable to implement for small organizations as it uses single server architecture. It can be used to automate deployments and script execution which helps users automate manual tasks. Jenkins is opensource and has a strong community which helps in resolving errors. Jenkins might not be suitable for large organizations or complex architectures. There are other competitors which might have an edge like Atlassian Bamboo/Octopus.

Use Cases and Deployment Scope

We use Jenkins as a main

CICD in our project, we organize jobs with similar function into Group, we

create jobs for the build, compile, and unit test each time a developer

check-in their code to a specified branch and build a new version of artifact

when having master branch commit.

We add some additional

plugin and create Jenkins jobs for run system test, automation test, and

integration test automatically when having new commit to master and have jobs

for deploy our new code to destination VMs on demand.

Likelihood to Recommend

Its' a good for continuous deployment, continuous integration, and continuous delivery also it's the best

integration tools in the market.

It also supports many plugins and it is targeting

users are developers and teams looking to automate parts of their software

development

process. If number of jobs are more this won't be that great application.

Use Cases and Deployment Scope

We use Jenkins to build and deploy all our applications. This range from web services, APIs, docker images, automated tests to small helper scripts. It automates all our build flows and make sure we always build using the same environment like most CI. As we have many applications depending on one API that have to be rebuilt every time, Jenkins provide us a cheaper alternative that is not dependent on build minutes.

Likelihood to Recommend

I think Jenkins is well suited if you are using a lot of build minutes and have to use your own hardware. It is also well suited if you need to customize your build and deploy process quite much, which is very possible with Jenkins. If your build and deploy needs are rather straight forward, it might be easier to just get a cloud service that provide you with easier to use interface and processes.

Use Cases and Deployment Scope

We used Jenkins to implement deployment automation through CI/CD

pipeline. Deployment has been easy now. We were building and deploying

our applications manually into DEV, test and PRD environments. It was

time consuming and it involved repetitive tasks, we used the jenkins to

remove all these manual tasks.

Likelihood to Recommend

Its easy to configure for simple pipeline deployment. Saves lot of time and manual efforts fir build and deployment.

Use Cases and Deployment Scope

We use Jenkins in our continuous integration pipelines. With Jenkins, we build and test our microservices. We also make extensible use of the plugin capability (we also develop and maintain internal plugins) to cover complex build/testing scenarios.

Likelihood to Recommend

Jenkins' strengths are:

<ul><li><b>Scripting</b>: Using Groovy we can extend the plugins' behavior and customize the way we build our projects. If you have complex pipelines and tricky build scenarios, please consider the use of Jenkins. </li><li><b>Maturity</b>: Nowadays we have powerful CI alternatives, but Jenkins is a tool used for many companies and has an active community so it's easy to find documentation related to almost any setup, also there are plenty of people with knowledge about it. </li></ul>Some areas where Jenkins needs improvement are:

<ul><li><b>Updating</b>: Jenkins needs to introduce/facilitate ways to update external dependencies.

</li><li><b>Scalability</b>: For some workloads, Jenkins still has issues with performance. </li></ul>

Use Cases and Deployment Scope

We utilized Jenkins to enable Continuous Integration and Deployment on 100s of our microservices. Deployed the Modular Pipelines architecture on Jenkins to enable seamless CI/CD between services utilizing different frameworks. So the thing is our pipelines facilitate the CI process from checking out code to building the artifact and then deploying it on Kubernetes.

Likelihood to Recommend

Jenkins is a highly customizable CI/CD tool with excellent community support. One can use Jenkins to build and deploy monolith services to microservices with ease. It can handle multiple "builds" per agent simultaneously, but the process can be resource hungry, and you need some impressive specs server for that. With Jenkins, you can automate almost any task. Also, as it is an open source, we can save a load of money by not spending on enterprise CI/CD tools.

Use Cases and Deployment Scope

My company uses Jenkins for building, testing, and deploying our projects. Since you can have all these plugins and works with GitHub, Jenkins seems to be the obvious choice. Jenkins also offers code quality as it has plugins to check the code. This helps us as we know if the Jenkins run fails or goes below the score quality, then we can catch major problems before they are deployed.

Likelihood to Recommend

Since I have worked with Jenkins, it has been reliable 9 out of 10 times. Considering you can build a docker file, test your code, have a sonar plugin for quality control, and then deploy the docker image all in one, this makes Jenkins very convenient to use. There have been times when Jenkins does not run. I am unsure if it is due to how many people are using the instance. It doesn't give a great description of why, which is the only time I have had negative issues with Jenkins.

Use Cases and Deployment Scope

The workflow begins with developers submitting pull requests containing their code changes and documentation. Jenkins automatically triggers builds, running unit tests to verify functionality and code analysis tools to assess quality and adherence to standards. Integration testing follows, ensuring seamless component interaction. User acceptance testing occurs in a dedicated environment, allowing stakeholders and users to provide feedback. Jenkins generates reports and notifications throughout the process, keeping stakeholders informed. Finally, upon review and approval, Jenkins handles the deployment to the production environment. This streamlined approach improves efficiency, consistency, and visibility, ensuring high-quality software releases.

Likelihood to Recommend

In a scenario where a small software development team is working on a simple project with minimal codebase and a straightforward deployment process, Jenkins may not be well suited. The overhead and complexity of setting up and maintaining Jenkins could outweigh the benefits of such a small-scale project. Additionally, the learning curve associated with Jenkins, along with its resource-intensive nature, might not be justifiable for a team with limited resources and a shared infrastructure. Alternative lightweight CI/CD solutions that offer streamlined workflows and require minimal configuration may provide a more suitable and efficient choice for small projects with straightforward requirements, focusing on simplicity, speed, and ease of use.