Launch a Debugging Terminal into GitHub Actions
blog.gripdev.xyz
Launch a Debugging Terminal into GitHub Actions
1–10 of 67 posts
Re: Launch a Debugging Terminal into GitHub Actions
#2Author here, this was something I wrote for fun/because I wanted to use it. Happy to answer any questions
Re: Launch a Debugging Terminal into GitHub Actions
#3I love this use of hole punching, also love how the author handled authentication.
I have definitely been in the position of needing to tweak a workflow over and over to get it to work, wasting hours when a terminal into the action would have allowed me to close the loop in minutes. Nice work to the author!
Re: Launch a Debugging Terminal into GitHub Actions
#4That'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
Re: Launch a Debugging Terminal into GitHub Actions
#5Author here, this was something I wrote for fun/because I wanted to use it. Happy to answer any questions
This is really awesome and I might try it (definitely bookmarked)
This might seem (offtopic?) but you mention railway and how for a 20mb app the costs become almost negligible and I got curious because I usually refer hetzner to be one of the cheapest but still good/well worthy solution
I find the pricing model of railway the most interesting. I am curious if you know of any other alternatives to railway which follow a similar pricing model as well as I'd like to compare if there are more of such cloud providers which provide this (preferably from a service which is more closer to bare metal than y'know cloud providers perhaps if that makes sense)
Re: Launch a Debugging Terminal into GitHub Actions
#6There are many tools and techniques like this. Not a nock against this tool, just an observation that we seemingly need these tools.
Is there no better way, GitHub?
Re: Launch a Debugging Terminal into GitHub Actions
#7That'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
Agreed. So much easier with self hosted runner. Just get out of your own way and do it. Use cases like caching etc also much more efficient on self hosted runner.
Re: Launch a Debugging Terminal into GitHub Actions
#8I'm using tmate for this: https://github.com/mxschmitt/action-tmate
Re: Launch a Debugging Terminal into GitHub Actions
#9Author here, this was something I wrote for fun/because I wanted to use it. Happy to answer any questions
This is really awesome and I might try it (definitely bookmarked) This might seem (offtopic?) but you mention railway and how for a 20mb app the costs become almost negligible and I got curious because I usually refer hetzner to be one of the cheapest but still good/well worthy solution I find the pricing model of railway the most interesting. I am curious if you know of any other alternatives to railway which follow…
Thanks! I'm not aware of others offering this pricing model
Re: Launch a Debugging Terminal into GitHub Actions
#10That 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 services learnt anything from CircleCI, it would be this single feature, because of the amount of hours it saved thousands of developers.
Lo and behold, when GitHub Actions first launched, that feature was nowhere to be seen, and I knew from that moment on that betting on GitHub Actions would be a mistake, if they didn't launch with such a table-stakes feature. Seems still Microsoft didn't get their thumb out, and wasting countless developer's time with this, sad state of affairs.
Thank you pbiggar for the time we got with CircleCI :) Here's to hoping we'll have CircleCI.V2 appearing at some point in the future, I just know it involves DAGs and "Rebuild with SSH" somehow :)