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

Re:Cache is King: A guide for Docker layer caching in GitHub... by ValtteriL on Sunday April 07, 2024 @01:23AM (#39958358)

Docker layer caching is one of the reasons I moved to Jenkins 2 years ago and have been very happy with it for the most part.

I only need to install utils once and all build time goes to building my software. It even integrates nicely with Github. Result: 50% faster feedback.

However, it needs a bit initial housekeeping and discipline to use correctly. For example using Jenkinsfiles is a must and using containers as agents is desirable.

[ Parent | on HN ]

Re:Cache is King: A guide for Docker layer caching in GitHub... by adityamaru on Sunday April 07, 2024 @01:26AM (#39958366)

do you self host your jenkins deployment in your AWS account?

[ Parent | on HN ]

Re:Cache is King: A guide for Docker layer caching in GitHub... by ValtteriL on Sunday April 07, 2024 @03:14AM (#39958843)

Self host

[ Parent | on HN ]

Re:Cache is King: A guide for Docker layer caching in GitHub... by remdoWater on Sunday April 07, 2024 @01:26AM (#39958370)

what do you mean by discipline here?

[ Parent | on HN ]

Re:Cache is King: A guide for Docker layer caching in GitHub... by ValtteriL on Sunday April 07, 2024 @03:27AM (#39958928)

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.

[ Parent | on HN ]