MetaCell / MetaCell/cloud-harness
Smarter build of cloudharness images
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 5
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 3
Description
Now images inherited from cloudharness are built regardless they are overridden or not.
We could preemptively build all cloudharness images for the main versions and use those prebuilt images instead of rebuilding them.
An idea could also be to tag images using a kind of hash on the content, so that same content is not built twice
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
The issue names no files, tests, or entry points, so first trace where inherited cloudharness images are selected and built. Clarify whether the goal is prebuilt images for main versions, skipping overridden images, content-based tags, or a combined approach; done should avoid redundant builds while preserving the required image versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100