Travis CI allows you to debug failing builds by getting SSH access to a container - https://docs.travis-ci.com/user/running-build-in-debug-mode/.
Concourse CI offers something similar with https://concourse-ci.org/builds.html#fly-intercept.
Would it be possible to allow a user to exec / SSH into a failing build to debug why it’s not working?
drone exec exists for this purpose but it has the following drawbacks:
- requires you to create a secrets file and copy all CI secrets whenever you want to debug a failing build which is a PITA
- does not use caching which means running locally might take a while until you get to the step you want to debug
- is only applicable to docker runners