Broken builds, found before standup
Failing builds and deployments across your repos, flagged every morning before standup
- Runs while your laptop is closed
- Reports in Littlebird and by email
- Free plan includes 5 routines
Two of 16 pipelines failed overnight, and the rest are passing.
- Web app, test stage: 12 sign-in tests are failing. The likely cause is Sam Ortiz's session change, merged at 11:40 PM.
- Billing service, deploy stage: the staging deploy failed at the database migration. The likely cause is Casey Reed's schema change from yesterday afternoon.
The problem
CI failures have a discovery problem: the build went red at 11pm, and the team finds out at 9am when someone tries to merge. Eight hours of compounding, zero hours of fixing.
The dashboard is always there. What is missing is the thing that watches the dashboard for you.
What it does
Every morning, this routine checks your pipelines and flags overnight failures: which repo, which stage, and the likely culprit change.
The red build gets eyes before standup. Main stays green, and 'works on my machine' stops being the morning's first message.
Try the prompt
Copy it into a new Littlebird routine, then set the days and times that fit your schedule
- Open Littlebird and go to Routines. Open the menu next to New Routine and choose Set up manually.
- Paste the prompt into Instructions, then set the days and time under Run.
- Littlebird runs it on schedule from then on. You can pause or edit it anytime. Auto-pause is on by default and pauses it if reports go unread.
You can also choose Create with Littlebird and describe the routine in chat.
Every morning check CI/CD status across all repos and flag any failing pipelines
Why make it a routine?
A chat can explain a failing build if you paste the log. It cannot notice that the build went red late last night.
This routine watches on a schedule and works from the pipeline status and changes already in your Littlebird context: which repo, which stage, and the likely culprit change.
The red build gets eyes before standup instead of at the first blocked merge.
Frequently asked questions
Which CI systems does it watch?
It works from GitHub, if you connect it, and from the build and deploy status already in your Littlebird context.
Can it page someone?
No. It reports failures to you on its daily schedule, so keep your paging tool for emergencies.
How long is the commitment?
Month to month if you like ($20), or $17 a month on the annual rhythm. Either way it starts with 14 free days. This routine also runs on the free Basic plan, which includes 5 routines.
Can I cancel anytime?
Yes. Try 14 days free, then Plus is $17 a month ($20 month-to-month), and you can leave whenever you want.
More routines like this one
Put Littlebird to work
Littlebird is free to start, and your routines also work on the web, iPhone and Android
.svg)
