GitHub Actions - VM console output

Published: 10 October 2025
on channel: Code Klaudia

When building this GitHub action, an ssh conection is established to connect to a Virtual Machine
In the video we see the console output of that VM
A t the end of this build the Virtual Machine is destroyed

There are 2 types of workflows :

1) workflow dispatch
2) server dispatch

Beware that when using workflow dispatch, there are 2 types of triggers :

on-pull
on-push

In this scenario the pipeline keeps waiting for the user to input variables, and the user might not see it

Runners, also called agents, are paid
Runners are similar to VMs and are always ephemeral
Runners are always deleted after the build and the content of the folders are not stored
For this reason, we always need to commit and push, so that evrything we did in the runner gets stores

Currently, as it stands, GitHub gives 500 runtimes for free
But in Production one needs to buy its own runners

https://github.com/code-klaudia-prog/...

DISCLAIMER :

In order to simplify the video, we have been using the correct git workflow
Always recall that in a corporative scenario, if you commit to the main branch, youre fired
Developent iterations are done with Feature-branches
Feature branches are usually deleted after erged with the dev branch
Although this is not mandatory, the good practices recommend that the commit message is not
longer than 72 characters

On this page of the site you can watch the video online GitHub Actions - VM console output with a duration of hours minute second in good quality, which was uploaded by the user Code Klaudia 10 October 2025, share the link with friends and acquaintances, this video has already been watched 27 times on youtube and it was liked by 0 viewers. Enjoy your viewing!