forked from ni/open-source
-
Notifications
You must be signed in to change notification settings - Fork 0
Toolchain & Runner Model
Sergio Velderain edited this page Aug 27, 2025
·
1 revision
Status: ✅ Stable Summary: The expected state of a Windows self-hosted runner and how we provision it deterministically.
| Category | Requirement |
|---|---|
| OS | Windows self-hosted runner |
| LabVIEW | Required versions and bitness installed |
| VIPM | Installed; runner_dependencies.vipc applied |
| G-CLI | On PATH (g-cli --help) |
| PowerShell | 7+ available |
| Node.js | 18+ available |
sequenceDiagram
participant M as Maintainer
participant R as Runner
M->>R: Install LabVIEW ("versions/bitness")
M->>R: Install VIPM and G-CLI
M->>R: Apply runner_dependencies.vipc
R-->>M: G-CLI on PATH
M->>R: Register self-hosted runner
See also: Runner Provisioning Contract
- Workflow Semantics & Reusable Actions
- Action Contracts (API)
- Quality Gates — Dev Mode and MIP
- Packaging & Release Artifacts
- Release Semantics & Versioning
- Matrix Strategy Patterns
- Local Parity How-To
- LVAddons — System-level Installation
- Hello LV Addon — Sample Skeleton
- Action YAML Snippets
- CI Log Snippets & Triage Examples
- Troubleshooting Signals
- Signals Catalog
- Release Hygiene Checklist
- Maintainer Print Checklists