remdoWater's comments

On: Cache is King: A guide for Docker layer caching in GitHub Actions

[remdoWater]

what do you mean by discipline here?

[ValtteriL → remdoWater]

Basically using exclusively declarative pipelines with Jenkinsfiles in SCM, avoiding cluttering Jenkins with tools aside from docker, keeping Jenkins up to date and protected with proper auth.

Jenkins is the most flexible automation platform and its easy to do things in suboptimal ways (eg. Configuring jobs using the GUI).

There's also a way to configure Jenkins the IaC way and I am hoping to dig into that at some point. The old way requires manual work that instictly feels wrong when automating everything else.

On: Cache is King: A guide for Docker layer caching in GitHub Actions

[remdoWater]

This requires a lot of work from a dev inf team, though. Not as straightforward for an average team.

[damianh → remdoWater]

I won't disagree. It should be easier imo. I guess this is why a cottage industry has sprung up addressing such e.g. https://news.ycombinator.com/item?id=39930908

[intelVISA → damianh]

Now I've seen everything...

[ownagefool → remdoWater]

It's actually pretty easy.

Setup GitHub app. Install the arc helm charts. Install a buildkitd statefulset.

Update parans on build to use buildkitd.

That's not to say there aren't better caching strategies, but a really basic ephemeral setup is right there.

[boundlessdreamz → remdoWater]

runs-ons supports custom images - https://runs-on.com/features/byoi/ and caching to S3 - https://runs-on.com/reference/caching/

I haven't used it yet but these two features make it the clear favourite for me in alternate github action runners

On: Cache is King: A guide for Docker layer caching in GitHub Actions

[remdoWater]

title suggestion: Cache Rules Everything Around Me (C.R.E.A.M.)