GitHub Actions - VM console output

Publicado em: 10 Outubro 2025
no canal de: 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

Nesta página do site você pode assistir ao vídeo on-line GitHub Actions - VM console output duração hora minuto segundo em boa qualidade , que foi baixado pelo usuário Code Klaudia 10 Outubro 2025, compartilhe o link com seus amigos e conhecidos, no youtube este vídeo já foi visto 27 vezes e gostou 0 espectadores. Boa visualização!

5,902

190