bridgewatch
A tray monitor for GitLab CI and GitHub Actions, for macOS and Linux. We wrote it because every monitor we tried read the newest pipeline on the branch, which on our project is the hourly schedule, and none could say what a push as a whole had done.
- trigger:websitedeploy:origins succeeded on four originsDeployed
- trigger:sentrysentry:apply failedFailed
- trigger:letterheadthree jobsPassed
Scheduled pipeline, 25 minutes ago, failed on purpose after correcting drift. Not counted: this watch follows pushes.
- Docker publishimage pushed to the registryDeployed
- CItwo jobsPassed
- Auditthree jobsPassed
Three workflow runs from one push, shown as one row.
Why another tray monitor
It sees the whole push
On GitLab it reads each child pipeline behind a trigger job. On GitHub, where one push starts several workflow runs that know nothing of each other, it folds them back into one row. Either way it can name the part that broke, and it notices a workflow that should have run and never started.
It knows a schedule from a push
A reconciler that fails on purpose should not turn your tray red all day. Each watch follows the sources you choose.
It answers "did it deploy?"
You name the jobs that mean shipped. The icon reports on those, and says so when something failed around them.
- Watches
- GitLab CI and GitHub Actions
- Licence
- Apache-2.0
- Built with
- Rust, Tauri 2, Svelte 5
- Ships as
- A signed macOS app for Apple silicon and Intel, and a .deb, an .rpm and an AppImage for x86_64 and arm64 Linux. The command-line tool builds from source.
Get involved
Issues and pull requests are welcome on GitHub. Report a vulnerability privately, as the security policy describes, and not in a public issue.
- Contributing guide
- CONTRIBUTING.md
- Security policy
- SECURITY.md
- Changelog
- CHANGELOG.md