git runner install on prod machine should be used to update runner install documentation
git runners should check commit message for so-signal, e.g., commit -m 'PROD ...' triggers Prod runner and DEV runner always gets triggered
- ssh gateway access is available
- git runner install on prod machine should be used to update runner install documentation
- git runners should check commit message for so-signal, e.g., commit -m 'PROD ...' triggers Prod runner and DEV runner always gets triggered
tar -xf node-v20.11.1-linux-x64.tar.xz --strip-components=2 -C ~/.local/bin/ node-v20.11.1-linux-x64/bin/
rm node-v20.11.1-linux-x64.tar.xz
Everything else was set up / executed in the prod runner.
Missing `node` installation on `prod` runner, see: https://gitea.psi.ch/sls/hla_framework_bd/src/commit/bc48934961e552af28b2a18016410225a61ce9a7/docs/developer/cicd_runner.md?display=source#L50-L57
Everything else was set up / executed in the `prod` runner.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Following:
f19b828cdc/docs/developer/cicd_runner.mdSetup hla dev/prod runnersto Setup hla dev/prod runners on `sls-vserv-bd-hla01(-dev)`Missing sudo permissions for
sudo dnf install act-runnerMissing
nodeinstallation onprodrunner, see:Everything else was set up / executed in the
prodrunner.