Jenkins pipelines

Earlier we have our Integration and Delivery pipelines chained together, taking code and producing and AMI artifact. Our next task is to design a third pipeline to take that AMI and deploy it into our production environment.

Before we can create the new job in Jenkins, we need to make the code for it available via Git:

Note

Please refer to: https://github.com/PacktPublishing/Implementing-DevOps-on-AWS/tree/master/5585_06_CodeFiles/CodeCommit/demo-app-cdeployment.

We will examine the files in detail shortly, for now just create and populate a demo-app-cdeployment CodeCommit repository. Similar to our other repositories, the new one would have an URL such as https://git-codecommit.us-east-1.amazonaws.com/v1/repos/demo-app-cdeployment.

With that in hand, we proceed to create the pipeline:

It will need to take an AMI ID parameter (to be passed on from the Delivery job):

Then of course, it needs the Jenkinsfile location (https://git-codecommit.us-east-1.amazonaws.com/v1/repos...