refactor: add 1-to-1 client-to-runner relationship into poller #1372
No reviewers
Labels
No labels
FreeBSD
Kind/Breaking
Kind/Bug
Kind/Chore
Kind/DependencyUpdate
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Windows
linux-powerpc64le
linux-riscv64
linux-s390x
run-end-to-end-tests
run-forgejo-tests
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo/runner!1372
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "mfenniak/forgejo-runner:multiconnect-multirunner"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When
NewRunneris invoked, it creates aRunnerwhich does client-specific configuration -- environment variablesGITHUB_SERVER_URL,ACTIONS_RUNTIME_URL, andACTIONS_RESULTS_URLare all different based upon the connection address to the remote client. Although thePollersupports multiple clients, it dispatches all the tasks to a singleRunnerinterface.This PR adds multiple
run.RunnerInterfaceimplementations to the poller, one per client, which are the runners created specifically for each client.cascading-pr updated at actions/setup-forgejo#884