News for hackers. Stuff that matters.
Re:Rails on Docker · Fly by claytonjy on Thursday January 26, 2023 @04:38PM (#34539192)
I never got around to implementing it but I wonder how this plays with cross-runner caches in e.g. Gitlab, where the cache goes to S3; there's a cost to pulling the cache, so it'll never be as fast as same-machine, but should be way faster for most builds, right?
Re:Rails on Docker · Fly by orf on Thursday January 26, 2023 @06:22PM (#34540285)
If you're running the CI inside AWS, and assuming the code isn't doing anything stupid, it will be fast enough for nobody to notice.
Re:Rails on Docker · Fly by maaarghk on Thursday January 26, 2023 @07:54PM (#34541113)
the cache is small but if you have a `docker buildx build --cache-from --push` type command it will always pull the image at the end and try to push it again (although it'll get layer already exists responses), for ~250mb images on gitlab I find this do-nothing job takes about 2.5 mins in total (vs a 10 min build if the entire cache were to be invalidated by a new base image version). I'd very much like it if I could say "if the entire build was cached don't bother pulling it at the end", maybe buildkit is the tool for that job
Re:Rails on Docker · Fly by claytonjy on Thursday January 26, 2023 @11:30PM (#34542490)
I mostly love Docker and container-based CI but wow what a great reminder that even common-seeming workflows still have plenty of sharp edges!