Setting up a Functional CI / CD pipeline

The first thing you need is a jenkins sever running in a public subnet. If you dont have that please refer to my github repo titled "jenkins-ec2". from the command line of your public server execute the following commands to get the follow softwares and set the rght permissons:

All these command can be provided as UserData when starting up your Ec2 instances

sudo yum install git -y
sudo yum install python3 -y
sudo amazon-linux-extras install docker -y
sudo yum install docker
sudo service docker start
sudo sytemctl enable dokcer
sudo usermod -aG docker jenkins
sudo usermod -aG docker ec2-user

The second thing you need is a second server in a private subnet. this will rpresent different stages such as dev, pre-production, and production. Again install the right softwares and dependencies:

All these command can be provided as UserData when starting up your Ec2 instances

sudo yum install git -y
sudo yum install python3 -y
sudo amazon-linux-extras install docker -y
sudo yum install docker
sudo service docker start
sudo sytemctl enable dokcer
sudo usermod -aG docker ec2-user

The next step is to access your jenkins server, using your_public_ip:8080. we theninstall the following plugins in our sever(Manage Jenkins -> Manage Plugins -> Avaialable):

Docker Commons Plugin
Docker Pipeline
Docker plugin
docker-build-step
CloudBees Docker Build and Publish plugin
SSH Agent

My Test script is dependent on the boto3 SDK (software development kit) to access AWS resources. I had to create enviromental variables, so that when Jenkis runs the test script if can properly communicate with our AWS resources. The following is an example of how to set that up (go to Jenkins -> Manage Jenkins -> Configure System -> Global properties -> Environment variables)

The Pipeline will build and push dokcer images to a docker hub repository. inorder to do this we must provide jenkis credentials to be able to do this in a secure manner. We also must allow give our jenkins sever an shh connection to our private ec2. So that it can stop and start new containers.

The next step is to create our pipeline.:

In our pipeline definition we will choose the option "pipeline script From SCM" - since we have a Jenkinsfile that will define our stages for us.
For the SCM field we will use the option "git" - You will have to give the repository url and sppecify on which branch a webhook will be listening on. In my case i used the dev branch.

Next we will create a webhook o that jenkins will pull and build the enviroment everytime that there is a push to a branch:

first we must go to the build trigger section of our pipeline, and select the option "GitHub hook trigger for GITScm polling"
Next we need to add the web hook to our github repo. To do this go to the settings of your github repo and go to the webhook section and add a web hook. the url should be like the follow "your_public_ip:8080/github-webhook".

Our jenkins file defines the stages that will take place. All we have to do now is run the pipeline.

mubtasims / jenkins_CI_CD

Setting up a Functional CI / CD pipeline

References

About

Languages