Re:We cut our CI pipeline execution time in half
by dijit on Friday February 17, 2023 @12:41PM
(#34837742)
Main reason is because honestly I'm too scared of a dirty filesystem wrecking builds.
[ Parent
| on HN ]
Re:We cut our CI pipeline execution time in half
by actionfromafar on Friday February 17, 2023 @12:45PM
(#34837818)
So, clean it, run in a tmpfs or whatever.
Re:We cut our CI pipeline execution time in half
by kvdveer on Friday February 17, 2023 @12:57PM
(#34837998)
Docker images in CI are typically just that: a tmpfs with a chroot and some network isolation. If you have it working once, youre pretty much guaranteed it will work again.
Doing this on bare metal with a script to clean the FS, ensure correct dependencies and maybe isolate the network (for safe unit tests), means you're just reimplementing much a non-trivial portion of docker or other container tools. Maybe that's worth it, but without justification, it just smells like risky NIH to me.