Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stage 6 of pinned builds takes a long time #1760

Closed
matthewdarwin opened this issue Oct 12, 2023 · 3 comments
Closed

Stage 6 of pinned builds takes a long time #1760

matthewdarwin opened this issue Oct 12, 2023 · 3 comments
Labels
more-info waiting for submitter to reply with more information

Comments

@matthewdarwin
Copy link

matthewdarwin commented Oct 12, 2023

Stage 6 of pinned builds takes a long time.... Is it possible to cache the results of previous builds so this doesn't need to take so long on subsequent builds?

image

@bhazzard
Copy link

@spoonincode can you take a look and determine if you think caching is something we can & should add to 5.0.0, or if there is another approach we should look into?

@spoonincode
Copy link
Member

fwiw this step (when completely fresh) takes sub 10 seconds on my box with the latest version of docker.

For me, with the latest version of docker, this step is properly cached. If you run the exact same docker build command a second time, you see it send the entire 2.7GB context again?

@spoonincode spoonincode added more-info waiting for submitter to reply with more information and removed triage labels Oct 16, 2023
@bhazzard
Copy link

bhazzard commented Jan 9, 2024

Closing as the docker does support caching.

@bhazzard bhazzard closed this as not planned Won't fix, can't repro, duplicate, stale Jan 9, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in Team Backlog Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
more-info waiting for submitter to reply with more information
Projects
Status: Done
Development

No branches or pull requests

4 participants