Skip to content

Commit c9665d9

Browse files
committed
Add README
1 parent 76eeb10 commit c9665d9

File tree

3 files changed

+19
-0
lines changed

3 files changed

+19
-0
lines changed

app_deployment_demo/README.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
# Ansible Tower Integration with Jenkins in CI/CD Process
2+
3+
Taking ideas from this blog [post](https://www.redhat.com/en/blog/integrating-ansible-jenkins-cicd-process), we will look at how Ansible Tower can be used for application deployment in a Continuous Integration/Continuous Delivery (CI/CD) process using a Jenkins Pipeline.
4+
5+
Jenkins is a well-known tool for implementing CI/CD. Shell scripts are commonly used for provisioning environments or to deploy applications during the pipeline flow. Although this will work, it is cumbersome to maintain and reuse scripts in the long run.
6+
7+
The purpose of using Ansible Tower in the pipeline flow is to reuse roles, playbooks and automation workflows for provisioning and application deployment so that Jenkins will not need to take on the role as a shell script executor.
8+
9+
While Ansible Tower can easily spin up the required infrastructure for on-prem and public clouds such as AWS, Azure and Google, this demo will only focus on the application deployment piece as we have already demonstrated infrastructure provisioning in other demos.
10+
11+
A generic CI/CD workflow using Ansible automation for Continous Deployment/Delivery is depicted in the diagram below (demo was done using Ansible Tower 3.8.0 with Ansible Engine 2.9.15)
12+
13+
![AnsibleJenkinsCICD](./images/ansible_jenkins_cicd.png)
14+
15+
The Jenkins pipeline flow is as follows
16+
17+
![AnsibleJenkinsPipeline](./images/ansible_jenkins_pipeline.png)
18+
19+
The other piece of codes that was used for the demo can be found at this [repo](https://github.com/eanylin/test-quarkus)
Loading
Loading

0 commit comments

Comments
 (0)