Which solution will implement this functionality with the LEAST operational overhead?
Create a custom test action for CodePipeline. Host the job worker on the on-premises server.
Use AWS CodeBuild and include the test checks. When the test checks clear, use AWS CodeDeploy to deploy and publish the code.
Create a custom test action for CodePipeline. Host the job worker on an Amazon EC2 instance to run the testing request.
Write test cases. Test the test cases locally before pushing the code changes to the version control.
Explanations:
Hosting the job worker on an on-premises server adds operational overhead and complexity by requiring management of the on-premises infrastructure.
Using AWS CodeBuild for test checks automates the testing process and integrates smoothly with CodePipeline. AWS CodeDeploy can handle deployment once tests pass, minimizing manual intervention.
Hosting the job worker on an Amazon EC2 instance adds unnecessary operational overhead. EC2 instances require maintenance and scaling management.
Testing locally before pushing code does not provide automation within the pipeline and delays the testing until after the code is developed. This is not integrated into the pipeline itself.
I estimate that the answer is:
Use AWS CodeBuild and include the test checks. When the test checks clear, use AWS CodeDeploy to deploy and publish the code.
I believe the answer is:
Use AWS CodeBuild and include the test checks. When the test checks clear, use AWS CodeDeploy to deploy and publish the code.