forked from ni/open-source
-
Notifications
You must be signed in to change notification settings - Fork 0
Matrix Strategy Patterns
Sergio Velderain edited this page Aug 27, 2025
·
1 revision
Status: ✅ Stable Summary: Choose a matrix that matches support policy: dual-bitness, multi-version, nightly schedules.
| Pattern | When to Use | Pros | Trade-offs |
|---|---|---|---|
| Single-version dual-bitness | Toolkits for x86 and x64 | One .vip, decent coverage | Packaging step longer |
| Multi-version single-bitness | Validate across 2021/2023 | Cross-version assurance | Longer wall time |
| Multi-version dual-bitness | Broad coverage | Max assurance | Highest runtime |
| Nightly matrix | Heavy builds/tests | Keep PR fast | Needs infra capacity |
strategy:
matrix:
bitness: [32, 64]
steps:
- uses: .../build-lvlibp@v1
with:
supported_bitness: ${{ matrix.bitness }}strategy:
matrix:
lv: [2021, 2023]
bitness: [32, 64]
steps:
- uses: .../run-unit-tests@v1
with:
minimum_supported_lv_version: ${{ matrix.lv }}
supported_bitness: ${{ matrix.bitness }}on:
schedule:
- cron: "0 3 * * *"See also: Workflow Semantics & Reusable Actions
- 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