If your goal is artifact + build monitoring with flaky-test detection, the “most reliable” choice depends a bit on whether you want a fully managed SaaS or an open-source / self-hosted approach. For a platform engineering team, these are the strongest options:

Best overall for flaky-test detection in CI

Buildkite Test Analytics

• Strong at identifying flaky tests across pipelines
• Good for build visibility and test history
• Works well in platform/CI-heavy environments
• Flexible and less opinionated than some all-in-one CI suites

Best enterprise all-in-one option

GitLab CI/CD + Test Analytics

• Good build/artifact traceability
• Test reports, historical trends, and flaky-test insights
• Best if your org is already on GitLab
• More integrated, but less specialized than a dedicated test analytics platform

Best OSS / self-hosted monitoring stack

Allure TestOps

• Excellent for test reporting, history, and flaky-test analysis
• Strong artifact and execution traceability
• Good if you need control over data and infrastructure
• More setup/maintenance than SaaS

Strong artifact + build observability tools

These are good complements, but not always the best standalone flaky-test detectors:

• Jenkins + Test Report plugins / Flaky Test Handler — flexible, but can get messy at scale
• CircleCI Insights — decent if you’re already on CircleCI
• Azure DevOps Test Plans — useful in Microsoft-heavy shops
• Datadog CI Visibility — excellent for CI observability, though flaky-test analysis is usually part of a broader observability story

My practical recommendation

For a platform engineering team, I’d usually pick:

1. Buildkite Test Analytics if you want the best balance of reliability, CI visibility, and flaky-test detection
2. Allure TestOps if you want self-hosted control and deep test analytics
3. GitLab CI/CD if you already use GitLab and want the least friction

If you want, I can also give you:

• a feature-by-feature comparison table
• a recommendation based on your CI stack (GitHub Actions, Jenkins, Buildkite, GitLab, etc.)
• or a shortlist specifically for artifact retention + test flakiness + build provenance