Automated Codefresh Pipeline Failure Alerts
Every few minutes, WebRun checks Codefresh for pipelines that just failed, posts the pipeline name, failing step, and commit to Microsoft Teams, and creates a Trello card so the fix is tracked from the moment the failure happens until it is resolved.
How do I get alerted immediately when a Codefresh pipeline fails?
WebRun checks Codefresh every few minutes for pipelines that just failed, posting the pipeline name, failing step, and commit to Microsoft Teams the moment it happens. It also creates a Trello card so the fix is tracked from failure to resolution, keeping a broken pipeline visible instead of just scrolling past in a busy channel.
- A failed pipeline gets a Teams alert within minutes
- Every failure has a tracked Trello card from start to fix
- No broken pipeline sits unnoticed in a busy channel
Built for Platform engineering teams · DevOps engineers · release engineers · Kubernetes teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
g.codefresh.ioin a real browser with your saved login - no setup, no API keys. -
1
Codefresh - check pipeline status
codefresh.io
WebRun opens Codefresh to check pipeline status. - Open Codefresh and check the status of pipelines across projects
- Identify any pipeline that just changed from success to failure
- Note the failing step, the commit, and the branch
Done when Every newly failed pipeline is identified with its failing step and commit.
-
2
Microsoft Teams - post the failure alert
microsoft.com
WebRun opens Microsoft Teams to post the failure alert. - Post an alert to the CI channel in Microsoft Teams
- Include the pipeline name, branch, failing step, and commit
- Link directly to the failed run in Codefresh
Done when The team has been alerted in Teams about the failed pipeline.
-
3
Trello - create the fix card
trello.com
WebRun opens Trello to create the fix card. - Open the Pipeline Fixes Trello board
- Create a card for the failed pipeline with the failing step and commit
- Place it in the To Fix column
Done when A Trello card exists for every newly failed pipeline.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will WebRun rerun the pipeline or push a fix?
No. It only alerts and creates a tracking card. Rerunning the pipeline or fixing the code stays with the developer who owns it.
Does it create a duplicate card for the same failure?
No. If a card already exists and is still open for that pipeline, WebRun will not create a second one for the same failure.
Which pipelines does it watch?
Whichever projects and pipelines you connect it to. You control the scope.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.