concourse / concourse/docker-image-resource
thoughts on using latest ECR remote cache support
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 162
- Forks
- 250
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
I want to be able to take advantage of newish buildkit feature that allows using remote cache while building. Since registry-image-resource doesn't support building and oci-build-task is behind on buildkit ( and seemingly unsupported ) this seems to be the place to enable this feature. This could speed up builds for at least all ECR users, but likely every repo going forward that supports this buildkit feature.
Describe the solution you'd like
Auto-detect that if registry is ECR, allow a flag to auto-enable remote cache usage when building
Describe alternatives you've considered
At least allow a cache_from and cache_to param that could support this feature, per the documentation
Additional context
No response
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 the registry-image-resource and the discussion of oci-build-task, then read the linked Amazon ECR remote-cache documentation. Compare the proposed ECR auto-detection with exposing cache_from and cache_to parameters; done means selecting and documenting a supported configuration for remote cache use during builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker, go
- Domain
- build-system, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100