-
A common workflow I use when debugging builds using other build tools is to inspect the workspace after a build has been completed. Sometimes it’s super useful to know what files are where, etc., and currently the only way I can see to do that in Actions is to alter my action to print out a directory listing. But that makes the develop/test loop for the build process quite long as I have to wait for another build to complete to get feedback. And I have no real way of printing out directory info if the build fails. Some other tools that provide solutions for this:
Is it posssible to get a solution to this? Also, does anyone know if there is documentation as to the state of the workspace between builds? Is a fresh VM used for each build? Is the workspace cleaned between builds? Any advice for build debugging in general would be appreciated. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
I put something together to help me debug Xcode build last week: https://github.com/csexton/action-debugger Supports linux and mac and can give you a ssh command to connect to the action and poke around. Should be able to use it by dropping |
Beta Was this translation helpful? Give feedback.
-
https://github.com/mxschmitt/action-tmate This allows you to SSH into the worker node. |
Beta Was this translation helpful? Give feedback.
-
uber essential tool ^^ oh my had i discovered this yesterday i wouldn’t have created a franken branch with erratic commits to bump the build bot and only be able to debug from self logged state in the VM… |
Beta Was this translation helpful? Give feedback.
https://github.com/mxschmitt/action-tmate
This allows you to SSH into the worker node.