Breakreport

Inspiration

Build failures create chaos:

• Developers scramble to share logs via Slack/email
• Critical error context gets lost
• Multiple people duplicate investigation work
• Historical failure knowledge disappears
• New team members can't learn from past issues
• Post-mortems lack comprehensive failure data

What it does

BreakReport automatically captures and documents every build failure in Confluence, transforming scattered information into organized, searchable knowledge that accelerates debugging and prevents recurring issues.

Every failed build automatically:

1. Captures complete build logs and error output
2. Analyzes error patterns and categorizes failure type
3. Extracts stack traces and diagnostic info
4. Identifies commits that triggered failure
5. Generates structured Confluence report
6. Creates searchable knowledge base entry

Result: Immediate access to complete failure context, collaborative debugging, institutional knowledge preserved.

How It Works

Developer Experience:

1. Build fails in pipeline
2. BreakReport notification appears in Confluence
3. Click link to view comprehensive failure report
4. Review logs, errors, recent commits
5. Collaborate with team via comments
6. Document resolution for future reference

Manager Experience:

1. Browse Confluence build failure space
2. Identify patterns and recurring issues
3. Track resolution times and owners
4. Make data-driven process improvements

Challenges we ran into

Using forge login command in a cloud IDE

What's next for Breakreport

Add capability to auto create issue in Jira alongside the report

Built With

• forge
• javascript
• typescript