Re:Launch a Debugging Terminal into GitHub Actions
by esafak on Monday January 12, 2026 @11:53AM
(#46591059)
I do not follow. How does that change anything? Don't things still go wrong? Do you not need to debug?
Re:Launch a Debugging Terminal into GitHub Actions
by maxloh on Monday January 12, 2026 @02:21PM
(#46592941)
Sorry for not being clearly enough.
The point is that it is very difficult to replicate the environment of a hosted GitHub Actions runner, and having to do so defeats the ease of use the platform provides.
Re:Launch a Debugging Terminal into GitHub Actions
by whynotmaybe on Monday January 12, 2026 @02:44PM
(#46593232)
I'm building and deploying appbundle from my self hosted runner for this exact reason.
I manually maintain flutter and Android sdk on my server.
I've never been a docker fan, I prefer to completely handle my whole stack.
I have scripts to install the required tools and some actions in my scripts are just echoing what needs to be done manually.
With the years, I've found that infra for fully reproducible builds cost too much to maintain for us.
That’s only true if you’re building simple workflows.
A counter-example would be a workflow that builds and uploads Android APKs. When I last checked last year, there weren't any well-maintained Docker images with the Android SDK pre-installed, and there are no updated, publicly available builds for the runner-images: https://github.com/actions/runner-images/issues/176