-
Notifications
You must be signed in to change notification settings - Fork 243
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
Caching for Haskell projects #318
Comments
OK, looks like I've cracked it:
Build time: 7.94 secondsKey changes:Cache the Optional improvements:Multi stage build that just copies the cc @coffee-cup |
Incredible! I can make that change today (unless you want to take it on). Thanks for doing the hard work and figuring this out. |
Feel free - I'm not a rust native just yet I'm afraid 😁
…On Fri, 15 Jul 2022, 17:45 Jake Runzer, ***@***.***> wrote:
Incredible! I can make that change today (unless you want to take it on).
Thanks for doing the hard work and figuring this out.
—
Reply to this email directly, view it on GitHub
<#318 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAVNVCAZ4AJUNKO2XLEOUTVUGISLANCNFSM53U32U6Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
actually contributing for this is relatively straightforward. You can take a look at |
Is there an existing issue for this?
Describe the bug
I'm trying to get caching working for Haskell projects.
Using the same basic haskell/servant project as #312 time I run
This gives me the following Dockerfile
This works building locally, but the cache doesn't appear to make any speed up (ghc is still downloaded and all library dependencies are rebuilt).
I think the haskell might work better if it did
stack install
and then called the executable from/root/local/bin
(I think).Or even better - use a two stage build and just copy the executable to the (much smaller) image that's pushed.
To reproduce
Use the command above to build a local docker file
Expected behavior
Caching should work
Environment
ubuntu
The text was updated successfully, but these errors were encountered: