Jenkins

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.

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.

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.

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.

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.