Skip to main content
Watchtower v0.7.0 connects GitLab alongside GitHub, finds flaky tests by running them again, rebuilds the Reports tab around the release verdict, lets you email results straight from the dashboard, and introduces paid plans. It also fixes every open issue in the connect-a-repository flow.

​
Connect GitLab

Connect gitlab.com projects with OAuth, or a self-hosted GitLab with an access token, from Settings → CI / Repos. Choose which projects to track, run Patrol on GitLab CI, and disconnect per account. GitLab projects appear alongside GitHub repositories everywhere: the test-source picker, Patrol, Reports, and Watchman.

​
Flaky-test checks and Signals

  • Run a Patrol 2x to 5x as a flaky check. Repeat runs are grouped in Past Runs and badged Flaky · N, Failing · N, or Same outcome. Open a group to see which tests changed outcome between repeats.
  • Turn on Run repeats in parallel to run each repeat as its own CI job. It finishes sooner and uses more CI minutes; leave it off when your tests share one remote environment or test account.
  • The new Signals page answers “what broke after working, and what looks flaky?” over the last 90 days of runs, with environment, type, and time-range filters.
  • Patrol CI dispatches faster, and an empty run history now explains why it is empty.

​
Reports, built around the verdict

The Reports tab now leads with the release decision: the GO / NO-GO verdict and its reason, then passed, failed, blocked, and pending totals, then Findings (failures first, then blocked, each with its error, recent pass history, priority, owner, and linked bug), then coverage by area and the facts of the run. Filter findings by type, by status, and by whether a bug is filed. PDF export uses a print palette, and totals only count tests that actually ran.

​
Email results from the dashboard

Click Email report on the Reports tab to compose a message, attach a run, preview it, and send; History shows what was sent and whether it was delivered. Every email Watchtower sends, including workspace invites and release verdicts, now reminds the sender that the recipient may need to check their spam folder.

​
Watchman

  • Link pull requests to tickets in both directions, with a Review Summary panel.
  • The Test Cases tab (formerly Test Run) gains a selection model, case-by-case review, a choice of which folder new cases land in, and a direct path to a case you just added.
  • Review the existing tests affected by a change, re-run only the selected cases, and confirm or unconfirm tickets reversibly.
  • The Unlink / Relink dialog shows the state of a pull request it already opened, and unlink state syncs back from the repository.

​
Plans and billing

Subscribe to a Pro or Team plan from the dashboard, manage invoices and cancellation in the customer portal, and see plan entitlements applied per workspace.

​
Dashboard and support

  • A support agent is available from the dashboard where your Watchtower instance has it enabled.
  • A beta feedback banner, a styled not-found page with a way back, and deep links that survive sign-in.
  • Trash appears once the dashboard has loaded, and Purge is offered only when there is something to purge.
  • Failed reads no longer appear as empty states.

​
Fixes

Connecting a repository:
  • Connecting from a staging or development environment returns you to that environment, including when you re-configure an installation that already exists.
  • Repositories connect into the workspace you are in, under the workspace owner, rather than into your default workspace.
  • The dashboard renders behind the test-source picker after the GitHub callback, instead of a blank area until the next click.
Settings and notifications:
  • Notification settings stay saved when the Settings modal reopens.
  • CI ingest honours your Block release / Warn only choice for NO-GO runs.
  • Help Center tabs without content are hidden until the content exists.
This release also includes security and reliability hardening across the API, workspace membership, invites, and repository connections.

​
Upgrade notes

GitHub repositories are connected into the workspace you are in when you click Connect. Switch to the workspace that should own the repository first; an invited admin’s connection lands in the owner’s workspace. See Workspaces.
If the Connect GitLab button is missing, or billing and the support agent are not visible, your workspace admin has not enabled them for your Watchtower instance yet. See Configuration.
If invite or report emails land in the recipient’s spam folder, ask them to mark the first one as “Not spam”; later messages will reach their inbox. Delivery itself improves as your instance’s sending domain builds reputation.
For the full documentation, start with What is Watchtower?. These guides cover v0.7.0, including GitLab connections, Signals, and billing. Earlier versions remain available in the version selector.