Repository navigation
[build] Only report build failures, not successes - #25959
Conversation
The 'Report build result' step no longer posts a GitHub comment when the build succeeds - only when it fails. These "Build passed" comments (and emails) don't add much value, so just remove them. We're still interested in failures though, so those will still be posted. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
This PR updates the Azure Pipelines build template to reduce noise by stopping the “Report build result” step from posting GitHub comments (and triggering notifications) on successful builds, while still reporting failures.
Changes:
- Add an early-exit in the “Report build result” PowerShell step when the job succeeds.
- Simplify the reporting logic to always construct a “Build failed” comment when reporting occurs.
This comment has been minimized.
This comment has been minimized.
✅ API diff for current PR / commitNET (empty diffs)✅ API diff vs stableNET (empty diffs)ℹ️ Generator diffGenerator Diff: vsdrops (html) vsdrops (raw diff) gist (raw diff) - Please review changes) Pipeline on Agent |
🚀 [CI Build #c021377] Test results 🚀Test results✅ All tests passed on VSTS: test results. 🎉 All 199 tests passed 🎉 Tests counts✅ assembly-processing: All 1 tests passed. Html Report (VSDrops) Download macOS tests✅ Tests on macOS Monterey (12): All 5 tests passed. Html Report (VSDrops) Download Linux Build VerificationPipeline on Agent |
The 'Report build result' step no longer posts a GitHub comment when the build succeeds - only when it fails.
These "Build passed" comments (and emails) don't add much value, so just remove them. We're still interested in failures though, so those will still be posted.
🤖 Pull request created by Copilot