Simply shutting down thousands of builds - the origin story of my first Big Red Button
| Website | https://sghill.net |
| Website | https://sghill.net |
Simply shutting down thousands of builds - the origin story of my first Big Red Button
Wrote about how we use support channels to prioritize high-leverage features.
Our support-driven features tend to require little effort, paying off the investment almost immediately. Yet they’re too small to be requested in more formal settings.
Favorite part of on-call is how many ideas are created to improve the system.
New blog post: Can our systems automatically validate intent?
Nearly done with our Jenkins JDK17 upgrade!
This migration required
• sequencing by component, risk
• changes made by partner teams
• progress reporting
• minimizing user impact
Many teams face the same challenges so I’m putting together a post about it. If you have questions the post could answer, or would be interested in reading a draft, please get in touch.
I’ve been modernizing some older #jenkins plugins with automated PRs.
3 changes that keep the build green is more consumable than 1 breaking change.
Today marks an awesome milestone!
Our v1.0.0 just got #released out into the wild.
Catch it if you can ... and play around, it got a ton of improvements over our old versions.
Also please #boost so everybody notice it.
#WoodpeckerCI #cicd #release #SelfHosting #awesome #coding #ci #cd
https://github.com/woodpecker-ci/woodpecker/releases/tag/v1.0.0
Impressed with the temporal.io courses. Easy setup, good structure.
Finished 101 yesterday and started on 102 today.
“What builds were running between 10:45 and 11:00?”
It used to take 30 minutes of groovy scripting to get a partial answer.
Today it’s a complete answer in seconds, because we store events for every build.
New blog post: What’s it like to get paged?
A platform operator cannot reasonably prevent unsupported use-cases. What now?
Look to the airplane ashtray for inspiration.