Jenkins

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.

• Faster deployments
• Reduced Human Errors & Downtime
• Standardization Across Teams
• Initial Setup Time is more

GitLab

Cursor, WebStorm

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.

• Scalability.
• Improved Code Quality and Reliability.

Atlassian Bamboo, GitLab and GitHub

GitLab, Atlassian Bamboo, GitHub

My team primarily uses Jenkins, an application deployment tool. We create automated jobs that test code and then deploy to servers/containers and restart the apps. We have also begun implementing several CI/CD uses where we are able to automate jobs to deploy container infrastructure code to Git and have runners automatically deploy into our environments.

• CI/CD
• Git Integration.
• Automated/Scheduled Jobs.
• Access Control.

• Improves Engineer to Dev efficiency.
• Maintains consistency between users.
• Provides project visibility.

Travis CI, GitLab and Azure DevOps Server

GitLab, ServiceNow IT Service Management, Venafi Control Plane for Machine Identities, Microsoft SharePoint

We use Jenkins in multiple ways. As part of the QA team, we use Jenkins to run all of our API tests automatically and report back to us. We have some tests that we have special emails for every time they run. We also use it to run our automated UI tests. On the dev side, we use Jenkins to control our builds; we have pipelines in place for our dev environments, qa environments, and formal and prod environments. We then can control which environments get built. We also have pipelines in place for after-power outages so that we can quickly and effectively bring all our servers back up, which run scripts to do so.

• Integrations with our tools.
• Plugins that work well.
• Easily configurable.

• We run about 30 test projects through Jenkins every day, multiple times a day; this allows us to focus on new tests rather than manually running all these tests.
• We rely heavily on reporting capabilities and email notifications; we have some jobs that send emails every time they run so we know if there is an issue with any of our services.

TriNet, ReadyAPI, SwaggerHub, mabl, TestRail, GitLab

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.

• It made very good impact in business by fastening the process
• It provides single place for building all the jobs
• I don't see any negative impact from Jenkins

GitLab

PagerDuty, Docker, Oracle Cloud Infrastructure, Google Cloud Build