How actions/runner works
Main Components
a. Core Runner Components:
• Runner Service/Daemon (Runner.Service)
• Runner Listener (Runner.Listener)
• Worker (Runner.Worker)
• Plugin Host (Runner.PluginHost)
• Common Infrastructure (Runner.Common)
b. External Integration Points:
• GitHub Actions Service
• Container Services (Docker)
• Source Control (Git)
• Artifact Storage
• Runner Registration System
Key Architectural Patterns to Highlight
a. Message-Based Architecture:
• Message listener pattern
• Job dispatch flow
• Demonstrate the broker message system
b. Plugin Architecture:
• Repository plugins
• Artifact plugins
• Custom action plugins
c. Container Management:
• Docker integration
• Container hooks
• Container operations
Specific Implementation Details
┌─ GitHub Actions Service Layer ─────────────────────┐
• Job Distribution │
• Authentication/Authorization │
• Runner Management │
• ┬───────────────────────────────┘
┌─ Runner Service Layer ──────────────────────────┐
• Runner.Listener │
• Message Processing │
• Job Dispatch │
• Self-Update Management │
• ┬──────────────────────────────┘
┌─ Execution Layer ────────────────────────────────┐
• Runner.Worker │
• Action Execution │
• Step Processing │
• Container Management │
• ┬──────────────────────────────┘
┌─ Plugin Layer ──────────────────────────────────┐
• Repository Plugins │
• Artifact Plugins │
• Custom Action Support │
• ┬──────────────────────────────┘
┌─ Infrastructure Layer ────────────────────────────┐
• Runner.Common │
• Authentication │
• Configuration │
• Logging │
• ┘
Flow Indicators
• Double lines: High-bandwidth data flow
Additional Elements
Specific callouts for:
• Security boundaries
• Authentication points
• Scaling components
• Error handling paths
• Update mechanisms
Implementation Details
• The separation between listener and worker processes
• The plugin architecture for extensibility
• The container execution environment
• The job execution pipeline
• The self-update mechanism
Critical Paths
Highlight:
• Job acquisition flow
• Action execution pipeline
• Plugin loading and execution
• Container lifecycle management
• Artifact upload/download paths
This system design should be created using a tool that supports:
• Nested components
• Relationship lines with different styles
• Text annotations
• Grouping of related components