letsencrypt / letsencrypt/boulder
Automate build and release of boulder-tools image
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
Currently we build and release boulder-tools manually using test/boulder-tools/tag_and_upload.sh. But we should automate that process to ensure builds are always made reproducibly and from a clean state. That would also let us remove some push permissions on Docker Hub.
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 reading test/boulder-tools/tag_and_upload.sh to understand the current manual build and release process. Determine how automation can produce boulder-tools reproducibly from a clean state and reduce Docker Hub push permissions. Done means the image build and release no longer depend on that manual process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, shell
- Domain
- build-system, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100