letsencrypt / letsencrypt/boulder
Use a Boulder container image as part of integration tests
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
Right now our integration tests run go install ./... inside a boulder-tools container, then run the resulting binaries. Instead, they should use the same build scripts that our release process uses to build a minimal Boulder container, and then run that container as the service for our integration tests to hit.
Followup to #8327
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the integration-test setup that runs go install ./... in the boulder-tools container, then compare it with the build scripts used by the release process. Check the follow-up issue #8327 for context. Done means the tests build a minimal Boulder container through the release scripts and use that container as the service they exercise.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- build-system, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100