letsencrypt / letsencrypt/boulder
Automatically rebuild local test docker image upon changes
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
It turns out that, even with a "build:" stanza in docker-compose.yml, the various docker compose commands won't automatically rebuild the container image unless no such image exists in the local cache. Instead, devs have to manually run docker compose build to get the latest version of the boulder-tools container.
https://github.com/letsencrypt/boulder/pull/7251 was an attempt to fix this, but it got bogged down in complex date fun times and making sure that the CI jobs don't rebuild the container.
When we have some time we should take another stab at fixing this automatically.
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 with docker-compose.yml and the approach in pull request 7251; compare how local docker compose commands build the boulder-tools image with the CI jobs. Done means local changes trigger an automatic image rebuild while CI jobs avoid unnecessary rebuilds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100