Menu

How to speed up GitHub Actions: cut a 25-minute pipeline, lever by lever
📰

How to speed up GitHub Actions: cut a 25-minute pipeline, lever by lever

DEV Community: cicd·Tom·4 days ago
#PFUCi6j1
#devtocicd#devto#dev#github#skipbox
Reading 0:00
15s threshold

A 25-minute GitHub Actions pipeline is usually four delays stacked: jobs waiting on each other, work that didn't need to run, setup that a blank VM repeats on every job, and CPU-bound steps squeezed onto 2 cores (a private repository's ubuntu-latest has 2 CPUs and 8 GB). Take them in this order. First, measure the critical path, with queue time apart. Then skip what didn't need to run, run independent jobs at once, stop rebuilding state, give the heavy steps more cores, and shard what is still long. The first three are workflow fixes that cost nothing. The rest are the machine: a runner that keeps its caches between jobs and has more cores.

Skipbox is that runner. Your jobs run on your account's own machine, which keeps Docker layers, package caches, tools and build output between jobs, with 4 to 16 vCPU, for a flat $39 a month with unlimited minutes. On astro's CI that was 528 s on GitHub and 30 s on Skipbox.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.