Which solution meets these requirements MOST cost-effectively?
Configure an Amazon EC2 instance with the CodeBuild agent to build the code.
Configure CodeBuild jobs on AWS for each branch build process.
Configure the CodeBuild agent to build the code in the local system.
Configure a Jenkins plugin for CodeBuild to run the code build process.
Explanations:
Configuring an EC2 instance with a CodeBuild agent would incur high costs due to the need for an always-on EC2 instance, making it less cost-effective compared to other solutions.
Configuring CodeBuild jobs for each branch allows for testing and building code before merging to the main branch, ensuring that developers don’t push broken code. This solution is cost-effective as it scales automatically based on needs and only incurs charges for actual builds.
Running the CodeBuild agent on local systems is not a scalable solution and would require developers to manage and maintain the agent locally, which is not efficient or cost-effective for a continuous integration process.
Configuring a Jenkins plugin for CodeBuild adds unnecessary complexity and overhead. Jenkins is an additional service that would require maintenance and resources, making it less cost-effective than using CodeBuild natively.
I sort that the answer is:
Configure CodeBuild jobs on AWS for each branch build process.
I outline that the answer is:
Configure CodeBuild jobs on AWS for each branch build process.