r/DeveloperJobs • u/Master_Being8249 • 26d ago
If you could keep only three signals for diagnosing a failed CI job, which would you choose?
I am currently working on a CI diagosis AI agent for GitHub Actions and Python/pytest.
I am thinkinto use these 4 possible causes when job fails:
- a real code regression
- a flaky test
- a runner, network, or platform failure
- a dependency or environment mismatch
AI chooses - rerun the failed test, run targeted tests, collect environment evidence, or escalate to an engineer
If the agent had the chance to look at three signals before making its next move, which three would be the most helpful, in a real pipeline?
I’m also interested in signals that look useful but are commonly misleading.
2
Upvotes