You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 7, 2024. It is now read-only.
Runners are small clients that connect to, check for, and execute tasks. The runner needs to be designed to run on arbitrary hardware with a variety of executors that actually execute the commands/code/etc.
Runners need to be registered with the orchestrator using a unique token. Once registered, the runner will check for tasks that match the tags (OS, executor), and execute those tasks.
Runners are small clients that connect to, check for, and execute tasks. The runner needs to be designed to run on arbitrary hardware with a variety of
executors
that actually execute the commands/code/etc.Runners need to be registered with the orchestrator using a unique token. Once registered, the runner will check for tasks that match the tags (OS, executor), and execute those tasks.
I think gitlab has a nice model to follow, which they use for their CI: https://docs.gitlab.com/runner/#runner-execution-flow
The text was updated successfully, but these errors were encountered: