Founder here. Debugging CI pipelines is a pain and it often feels like a slow, unproductive printf() debugging process. All of us who have gone through the tedious cycle of run->fail->log->fix->run->fail-> can attest to the massive waste of time it creates.
To change this, we built Trunk's CI Debugger. We initially built this for Trunk because we found that CI jobs were not stable and took multiple hours to track down the root cause of failure. The debugger gave our team a way to add conditional breakpoints, receive alerts on and debug our CI like you do your code.
You can see how this works for GitHub Action in our repo: https://github.com/trunk-io/breakpoint, but it works with any CI system you use - Jenkins, GitHub Actions, Buildkite, Circle CI.
To get started, check out our CI Debugger in the link above. We learned a ton building this tool, and I would love to hear your feedback and answer any questions you might have. Here's to making the debugging process in CI systems as seamless as it should be.
