You are using Jenkins as your continuous integration systems for the application hosted in AWS.
The builds are then placed on newly launched EC2 Instances.
You want to ensure that the overall cost of the entire continuous integration and deployment pipeline is minimized.
Which of the below options would meet these requirements? Choose 2 answers from the options given below.
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - A and C.
To ensure low cost , one can carry out the build tests on the Jenkins server itself.
Once the build tests are completed , the build can then be transferred onto newly launched EC2 Instances.
For more information on AWS and Jenkins, please visit the below URL:
https://aws.amazon.com/getting-started/projects/setup-jenkins-build-server/Option D is incorrect.
It would be right choice in case the requirement is to get better speed.
To minimize the overall cost of the continuous integration and deployment pipeline using Jenkins, we need to consider a few factors such as the cost of running Jenkins, the cost of running EC2 instances, and the cost of running the build tests.
Option A - Ensure that all build tests are conducted using Jenkins before deploying the build to newly launched EC2 Instances.
This option implies that the build tests are conducted on the Jenkins server, which could be an EC2 instance or a standalone server. Once the build tests are completed, the build is then deployed to the newly launched EC2 instances. This option is cost-effective as the build tests are conducted on the Jenkins server, which is already running, and there is no need to launch additional EC2 instances. Additionally, this option reduces the risk of errors or issues arising during deployment as the build has already been tested.
Option B - Ensure that all build tests are conducted on the newly launched EC2 Instances.
This option implies that the build tests are conducted on the newly launched EC2 instances, which are then used for the deployment. This option is not cost-effective as we need to launch additional EC2 instances for each build test, increasing the overall cost of the pipeline.
Option C - Ensure the Instances are launched only when the build tests are completed.
This option implies that the EC2 instances are launched only when the build tests are completed. This option is cost-effective as we are not keeping EC2 instances running when they are not required. However, this option may increase the overall turnaround time for the pipeline as we need to wait for the EC2 instances to launch before deploying the build.
Option D - Ensure the Instances are created beforehand for faster turnaround time for the application builds to be placed.
This option implies that the EC2 instances are created beforehand and kept running to reduce the turnaround time for deploying builds. This option is not cost-effective as we are keeping EC2 instances running when they are not required, increasing the overall cost of the pipeline.
Therefore, options A and C are the best choices to minimize the overall cost of the continuous integration and deployment pipeline using Jenkins. Option A ensures that build tests are conducted on the Jenkins server before deployment, while Option C ensures that EC2 instances are launched only when they are required.