Jenkins

We use Jenkins to build and deploy AEM (java/maven) applications. We usually stand up one instance per project so that teams do not interfere with each other. At the end of the project we destroy those instances. It is used primarily for CI to dev and qa environments, and final build package delivery. It integrates with our package management system Artifactory.

We have been able to leverage existing free plugins, and not needed to write any custom or convoluted scripts.

Jenkins is an extremely powerful continuous integration/continuous delivery tool. It can be used to automate a very diverse set of operations - including, but also well beyond, application deployments. This is thanks to amazing flexibility and the impressive number of available plugins.

In the traditional sense, Jenkins easily addresses the following problems:

• Build and release automation
• Test automation with result report generation
• Test coverage reports
• Version control polling
• Status notifications
• Conditional, concurrent and branched pipelines
• Master-slave architecture
• Credentials storage
  
• Really, any custom scheduled or event-driven (primarily via version control events) workloads - of course don't go crazy with that, you don't want to schedule data science jobs on Jenkins for example. Key word is "operations".
  

Thanks to its large community and amount of available plugins, you can easily:

• Integrate with Slack to push notifications, also true for many other chat services
• Integrate with GitHub, GitLab, Bitbucket via hooks (as opposed to polling)
• Create and restore backups
• Integrate with external authentication providers (e.g. OAuth)
• Define your pipelines as code

Jenkins runs our continuous delivery and deployment pipelines for multiple on-premise environments. Through the use of its plugins, we're able to extend its capabilities.

We use this technology throughout the company. Most of the time we integrate this with Git. Just by installing a Git plugin to the dashboard we are ready to rock and automate. We do the following process (this step by step guide will brief you more on our work): 1. Install and Integrate Git plugin with the dashboard of Jenkins (localhost:8080), 2. provide the URL/repository URL, 3. git pulls request so as to sync save all data to Jenkin workspace, 4. go to SCM, and select Git in freestyle project, 5. execute the operations and some batch commands, and 6. you are done! Now you are ready to automate your tests (Plugin wise) and debugging. We mostly use mailer application which triggers a mail to all the recipients when our production code builds successfully.

We use it across all the dev org. Maintenance is pretty straight forward and there are so many plugins to choose from. We have about 20-25 build machines that are continuously running jobs. It has so many hooks for svn.