Run docker build less often
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 2h 41m
- Merged PRs (30d)
- 66
Description
Currently, the slowest GitHub actions are the docker builds. The only ways the docker builds would fail are:
- a new top level file or directory that is COPY-ed is added or removed
npm ciornpm run buildfailcargo buildfails- the Dockerfile includes changes that need iteration
npm ci/run build and cargo build are covered directly by other GitHub actions
In order to mitigate against merging breaking changes to main, we could run the docker builds IFF the list of top level files has changed, or if the Dockerfile has changed
Contributor guide
No contributing guide indexed for this repository
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
Inspect the GitHub Actions workflow that invokes the Docker builds and the Dockerfile; start by mapping the top-level files used by COPY and the existing npm and cargo checks. Done when Docker builds run only when those inputs or the Dockerfile change, while the separate npm and cargo checks remain responsible for their failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, rust
- Domain
- build-system, ci-cd, devops
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100