Working with Microservices-11: Creating an ECR repository and Preparing Production Pipeline scripts

We will prepare script files to run in the Jenkins pipeline, and then we will do packaging, tagging, pushing, and deploying with these script files. We will create an ECR repository to save the images. Then, we will prepare a Jenkins file and then create a Jenkins Production pipeline by using them. We will do it all step by step.

Topics we will cover:

1. Connecting to the Jenkins interface

2. Creating a repo on AWS ECR using the Jenkins pipeline for the production stage

3. Preparing a script to create AWS ECR repo tags for the Production docker images

4. Preparing a script to build the Production docker images

5. Preparing a script to push the Production docker images

6. Preparing a script to deploy application to production environment (Kubernetes cluster)

7. Preparing a script to package the microservice app with Maven

8. As a result

9. Next post

10. References

In our previous article “Working with Microservices-10: Explanation of the Production Stage and Creating Amazon EKS cluster for the “Production Environment and Pipeline in order to deploy the Microservices App into it”, we created an Amazon EKS cluster for Jenkins Production Pipeline and prepared a source code management repository (GitHub). And we talked about the Production Stage and the DevOps tools we will use. Now, we continue from where we left off.

1. Connecting to the Jenkins interface

Copy your Jenkins server’s public IP, as shown in Figure 1.

In order to connect to Jenkins, enter into your browser: http://<your_server_public_ip>:8080, then enter your admin and password values, and click on the sign-in button, as shown in Figures 1–2.