We’re now on the fifth episode of Semaphore Uncut, our weekly show where we talk about continuous integration, continuous delivery and Semaphore 2.0. This time around, you’ll see how to quickly jump into a finished CI job that failed and debug it.
How to quickly debug jobs in Semaphore 2.0
Last week, we showed you how to attach to a running CI job and debug it. In this episode, you can take a look at simple on-demand debug sessions in Semaphore:
Feel free to share any questions or suggestions on debugging and future episodes in the comments below.
Happy building, and see you next Wednesday!
Read/watch next
- Introducing Semaphore 2.0, Next Generation CI/CD
- Semaphore Uncut: A First Look at Semaphore 2.0
- Semaphore Uncut: Auto-promotion of Continuous Delivery Pipelines
- Semaphore Uncut: Customizable CI/CD Dashboards
- Semaphore Uncut: Debugging Running CI Jobs
Want to discuss this article? Join our Discord.
