It’s also massively more performant
122 karma · joined November 16, 2021
It’s also massively more performant
Wrap your GH Actions in a debugger breakpoint and connect into the live broken GH Action to inspect the machine, re-run commands etc..
At it's heart - realtime debugging for GitHub actions.
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.
With the debugger, you set conditional rules like - 'if this fails - then trigger debugger and hold machine' - instead of trying to catch lightning in a bottle - it waits for you.
More details and sign-up here https://ci-debugger.io