zstd layers for quantecon-build, plus a tag input for test-container.yml
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 1
- Avg merge
- 32m
- Merged PRs (30d)
- 3
Description
From #92 Phase 1: zstd-compressed layers for quantecon-build in build-containers.yml, worth −20–35s per PR pull (measured pull is 129s, 75% of a warm lecture-dp run).
Neither docker/build-push-action call sets outputs: (.github/workflows/build-containers.yml:66-74, :108-116), so both push default gzip.
- Add a tag input to
test-container.yml— itsworkflow_dispatch:takes noinputs:(:6-11) and:latestis hardcoded at:33,:99 - Push a
:zstdtag and validate it with the smoke suite before:latestmoves —:latestreaches consumers ungated by any release (see #92's note against #135) - Flip the build to zstd layers once validated
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 .github/workflows/build-containers.yml:66-74 and :108-116, then inspect .github/workflows/test-container.yml:6-11, :33, and :99. Trace how the tag input and build outputs flow through the smoke suite, and verify the zstd-tagged image before :latest is updated. Done means both build calls use validated zstd layers and the test workflow can select a tag.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100