Live data from Hacker News

Launch a Debugging Terminal into GitHub Actions

blog.gripdev.xyz

21–30 of 67 posts

Re: Launch a Debugging Terminal into GitHub Actions

#21

Earlier quoted context omitted.

> Is there no better way, GitHub? CircleCI solved this anno 2011, with "Rebuild with SSH". Microsoft asleep at the wheel as usual, not sure it's unexpected at this point.

The more you have to rerun your actions to debug them, the more money Microsoft makes. They aren’t incentivized to save you time.

Completely bonkers that people, companies and organizations just swallow this, bait and all.

Re: Launch a Debugging Terminal into GitHub Actions

#22
post #19

That's my hill to die on : you must have a self hosted agent. You can have many cloud agents as you wish but you must at least have one where you can remotely connect. It has saved me hours of troubleshooting and polluting "workflow v1.3.56_final_should_work_2" commits

> That's my hill to die on : you must have a self hosted agent. 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-im…

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

#24

Earlier quoted context omitted.

The more you have to rerun your actions to debug them, the more money Microsoft makes. They aren’t incentivized to save you time.

Completely bonkers that people, companies and organizations just swallow this, bait and all.

Free hosting, CI minutes, and an ecosystem.

Re: Launch a Debugging Terminal into GitHub Actions

#25

That the entire ecosystem seems to have moved to GitHub Actions is such a loss for productivity. I remember when CircleCI first launched, and you could "Rebuild with SSH" which gave you a bash command to connect to the running instance whenever you wanted, was such a no-brainer, and I'm sure why many of us ended up using CircleCI for years. Eventually CircleCI became too expensive, but I still thought that if other s…

I am surprised Docker didn't launch into the CI market. Running a container build as CI seems like it would both be a boon for simplifying CI caching and also debugging since it's ~reproducible locally.

They _are_ in the CI market. Two of their products are the Docker Build Cloud and Testcontainers Cloud. IIRC Docker Hub also came with automated builds at some point (not sure if it still does).

I do get your sentiment tough. For the position they are in, a CircleCI-like product would seem to be quite fitting.

Re: Launch a Debugging Terminal into GitHub Actions

#26
post #24

Earlier quoted context omitted.

Completely bonkers that people, companies and organizations just swallow this, bait and all.

Free hosting, CI minutes, and an ecosystem.

Commit and push to test small incremental changes, self-hosted runners' time still count towards CI minutes, and an ecosystem hellbent on presenting security holes as new features. I'm a bit unimpressed :)

Re: Launch a Debugging Terminal into GitHub Actions

#27
post #8

I'm using tmate for this: https://github.com/mxschmitt/action-tmate

I'll second this.

I've used this action to debug builds, and it works beautifully.

However, I've had to stop because the action isn't a 'verified' action and corporate policy.

I'd love to see github themselves offer something like this.

Re: Launch a Debugging Terminal into GitHub Actions

#28
post #25

Earlier quoted context omitted.

I am surprised Docker didn't launch into the CI market. Running a container build as CI seems like it would both be a boon for simplifying CI caching and also debugging since it's ~reproducible locally.

They _are_ in the CI market. Two of their products are the Docker Build Cloud and Testcontainers Cloud. IIRC Docker Hub also came with automated builds at some point (not sure if it still does). I do get your sentiment tough. For the position they are in, a CircleCI-like product would seem to be quite fitting.

Wow you're right they are. Yeah, they could really use some improvement there.

https://docs.docker.com/build-cloud/ci/

This could've been a "change runs-on to be this" like all the other faster GHA startup products, but instead the way they set it up I would have to keep paying for GHA while also paying for their build cloud. No fun!

Re: Launch a Debugging Terminal into GitHub Actions

#29

That the entire ecosystem seems to have moved to GitHub Actions is such a loss for productivity. I remember when CircleCI first launched, and you could "Rebuild with SSH" which gave you a bash command to connect to the running instance whenever you wanted, was such a no-brainer, and I'm sure why many of us ended up using CircleCI for years. Eventually CircleCI became too expensive, but I still thought that if other s…

Still using CircleCI. I do not love YAML at all, in fact I hate it because it's basically a 1980s text preprocessor on steroids and with dependency management. Too much logic applied to config that depends on implicit syntax and unintuitive significant whitespace.

I mean, I had an issue once where this broke the pipeline:

   key:
     - value 1
     - value 2
But this was fine:

    key:
    - value 1
    - value 2
Fuck that noise!

Otherwise it works just as good as it ever did and I don't miss Github Actions where every pipeline step is packaged into a dependency. I think Github has stagnated harder than CircleCI.

Re: Launch a Debugging Terminal into GitHub Actions

#30
post #8

I'm using tmate for this: https://github.com/mxschmitt/action-tmate

I'll second this. I've used this action to debug builds, and it works beautifully. However, I've had to stop because the action isn't a 'verified' action and corporate policy. I'd love to see github themselves offer something like this.

The neat part is you can do whatever you want in a GitHub action, corporate policy be damned. So:

git clone cd Run the action start point.

Apparently this is a feature, not a security risk.

https://blog.yossarian.net/2025/06/11/github-actions-policie...

Post reply on HN