Cache the builds so that we can do Incremental builds instead of a full rebuild every time
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, dockerfile
- Domain
- build-system, devops
Research direction
Start by reading the repository's Docker build and container configuration to understand where SDKs and the full repository are cloned. Implement persistent volumes for the containers so subsequent builds reuse the repository and SDK data instead of cloning everything again. Done means incremental builds reuse cached data while the existing engine builds and unit tests still run successfully.
Written by the indexing model from the issue text.
Description
Right now we clone all the SDKs and the full repo. We should just use volumes for each container to cache the build and the repo
- Dominant language
- Dockerfile
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from flingengine/FlingDockerBuild
-
enhancement help wanted
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in flingengine/FlingDockerBuild
Similar issues
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oSoWoSo/vOid_Community_repOsitory#240 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
self-care self-care:docs-build-time-investigator
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-cao#15846 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 3 days
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
RedHatOfficial/aap-demo#211 ·
Maintainers usually reply within 1 day