Run integration tests with custom containers
0
As a PoC I want to build a pipeline for GitOps of policy management. When a policy is committed to a repo, I want to run an existing Docker container (available on Docker Hub) that acts as a policy engine with a REST API exposed for uploading the policies and then run queries against. What is the easiest way to accomplish this?
- Commit policies to Git (preferably CodeCommit)
- Spin up a prebuilt Docker container
- Run a shell script with curl commands to upload and test the validity of the policies on the Docker container
- Fail the pipeline if curl does not return 200.
質問済み 9ヶ月前272ビュー
2回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
Would something like this be the right approach to run the container inside the build?
version: 0.2
phases:
install:
runtime-versions:
docker: 24
pre_build:
commands:
- docker pull my-docker-image:tag
- docker run -d --name policy-container my-docker-image:tag
build:
commands:
- sh integration_tests.sh
post_build:
commands:
- docker stop policy-container
- docker rm policy-container
回答済み 9ヶ月前
0
You can use AWS CI/CD stack: CodeCommit, CodeBuild, CodePipeline.
https://aws.amazon.com/codecommit/
https://aws.amazon.com/codebuild/
https://aws.amazon.com/codepipeline/
In a buildspec you can define all the needed commands:
https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html
回答済み 9ヶ月前
The latest version is docker: 20 in a buildspec. To avoid limits you need to log in:
version: 0.2
env: secrets-manager: DOCKERHUB_PASS: "/dockerhub/credentials:password" DOCKERHUB_USERNAME: "/dockerhub/credentials:username" phases: install: commands: - echo pre_build step... - docker login --username $DOCKERHUB_USERNAME --password $DOCKERHUB_PASS - $(aws ecr get-login --no-include-email --region us-east-1)
In general, your buildspec is fine.