Frequently Asked Questions
What permissions does CI/CD Watch need?
We request read-only access to your repository metadata and pipeline runs. The specific permissions depend on your provider (GitHub, GitLab, Bitbucket, CircleCI, Azure DevOps, or Jenkins), but we never access your source code, issues, or pull requests.
Can I monitor private repositories?
Yes. As long as you have access to the repository on your CI/CD provider, you can monitor it on CI/CD Watch.
How real-time is the dashboard?
Pipeline run updates appear within seconds of status changes. We poll your provider's API at short intervals to keep your dashboard current.
Is there a limit on repositories?
The free tier supports up to 3 repositories. Upgrade to Team for 20, Business for 100, or Enterprise for unlimited. See pricing for details.
Can I share the dashboard with my team?
Yes. CI/CD Watch supports team workspaces. Invite team members from the settings page and they'll share your workspace — same connections, same repositories, same dashboard view. Admins can manage members and invitations.
What are DORA metrics?
DORA metrics are four key measures of software delivery performance: Deployment Frequency (how often you deploy), Lead Time for Changes (time from commit to production), Change Failure Rate (percentage of deployments that cause failures), and Mean Time to Recovery (how quickly you recover from failures). CI/CD Watch calculates these automatically from your pipeline data. Learn more in our DORA metrics documentation.
What does flaky, broken, or healthy mean?
These are pipeline stability classifications. A healthy pipeline passes consistently. A flaky pipeline alternates between passing and failing — indicating intermittent issues like timing-dependent tests or resource contention. A broken pipeline is failing consistently and needs immediate attention. The flip rate measures how often a pipeline switches between states. This same classification applies to individual test cases.
How do I configure which repositories are monitored?
Go to Settings, select a connection, and you'll see your organizations and repositories listed. Check the ones you want to monitor and uncheck the ones you don't. Changes take effect immediately.
Can I connect multiple providers at once?
Yes. You can connect GitHub, GitLab, Bitbucket, CircleCI, Azure DevOps, and Jenkins simultaneously. All your repositories appear in a single unified dashboard regardless of which provider they come from.
What is pipeline performance analysis?
Pipeline performance analysis tracks how long your pipelines take and whether they're getting slower. Each pipeline gets a performance rating (fast, acceptable, slow, or critical) based on its median duration. p95 tracking catches outlier runs, degradation alerts flag pipelines that are slowing down, and optimization suggestions help you fix the root cause — like parallelizing jobs or adding caching.
How does test result tracking work?
CI/CD Watch automatically parses JUnit XML reports published by your CI pipelines to surface test failures, error messages, and stack traces. Each test is classified as healthy, flaky, or broken based on its recent history. Learn more about flaky test tracking.
What is Picture-in-Picture mode?
Picture-in-Picture (PiP) pops out a floating mini-dashboard that stays visible while you work in other tabs or applications. It shows live build metrics — running, failed, and total counts — plus your most recent builds with status and duration. Click the PiP button in the top navigation to open it.
Can I view my pipeline configuration files?
Yes. CI/CD Watch fetches your CI/CD configuration files (GitHub Actions workflows, GitLab CI YAML, etc.) and displays them directly in the app. The config viewer is available from the Performance, Stability, and Data pages — click the config icon on any pipeline to inspect its workflow definition without switching to your repository.