Menu

My Runs Took 19 Hours, My Measurement Counted 58,530
πŸ“°

My Runs Took 19 Hours, My Measurement Counted 58,530

DEV Community: cicdΒ·Mustafa ERBAYΒ·1 day ago
#FgB6n33I
#devtocicd#devto#dev#runs#days
Reading 0:00
15s threshold

Two weeks ago I audited the claims in this blog's agent instructions one by one

against the code. The one that mattered most in that audit was deploy duration :

the docs said "about 12 minutes" in five separate places, and measuring twenty-four

runs gave a median of 3.3 minutes. That was one workflow. This morning the question

was wider: how much machine time do all of the repository's workflows consume?

Measuring looked easy. The GitHub Actions API gives timestamps for every run;

subtract created_at from updated_at and you have the duration. One line of

Python, one coffee. I pulled the last thousand runs, summed the differences, and the

screen told me: 58,530 hours . Six and a half years. Across fifteen days.

The number was so absurd that it saved me. I wish every bad measurement were wrong

that loudly; most of them look plausible, settle into a dashboard and quietly bend

decisions.…

Continue reading β€” create a free account

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