pipeline-monitor

To track CI/CD build success rates and find flaky tests, this Skill analyzes pipeline logs to monitor successful build percentages over time and pinpoint tests that fail intermittently. It works across GitHub Actions, GitLab CI, and CircleCI to indicate test instability.

Yes, CI/CD pipeline monitoring works with GitHub Actions, GitLab CI, and CircleCI. The Skill analyzes build performance, identifies flaky tests, and tracks duration trends across these specific continuous integration platforms to provide actionable insights.

A flaky test fails intermittently, indicating instability in your pipeline. Identifying flaky tests is crucial because they disrupt build duration trends and overall pipeline stability, allowing teams to prioritize fixes and investigate performance bottlenecks effectively.

To analyze CI/CD pipeline performance for the current repository, you initiate a quick start analysis that parses logs efficiently using caching to minimize token usage. This provides actionable insights into build success rates, flaky tests, and duration trends.

The best way to minimize token usage when parsing CI/CD build logs is to leverage caching and efficient log parsing techniques. This Skill uses these methods to track build success rates and identify flaky tests while providing actionable pipeline insights.

Your CI/CD pipeline has intermittent build failures and increased build times likely due to flaky tests and performance degradations. By analyzing build duration trends and identifying intermittently failing tests, you can pinpoint instability and prioritize fixing bottlenecks.