Summary
Implement container/version signaling and host/runtime separation for NSIS and build-spec execution.
Required policy changes
- Host OS NSIS path must only use LabVIEW 2020.
- Any LabVIEW version other than host-2020 must run via Docker.
- Docker image version must be derived from
labview-icon-editor/.lvcontainer at clone time.
.lvcontainer raw text must be imprinted into the job name.
- Derive and imprint bitness in the job name to indicate which LabVIEW bitness the container used for build-spec (PPL) execution.
- Add a placeholder lane for source-distribution build-spec execution (similar style to
Apply VIPC).
Acceptance criteria
- Workflows enforce host-only LV2020 for NSIS installer path.
- Non-2020 build-spec lanes resolve container tag from cloned
labview-icon-editor/.lvcontainer.
- Job names include
.lvcontainer text and derived bitness.
- PPL build-spec lane explicitly reports container bitness used.
- Source-distribution placeholder lane exists and emits deterministic status/artifacts (Apply VIPC-style contract).
- Contract tests cover these rules and fail on regressions.
Notes
Opened as requested to track this as a dedicated change set rather than mixing into current gate stabilization/merge lane.
Summary
Implement container/version signaling and host/runtime separation for NSIS and build-spec execution.
Required policy changes
labview-icon-editor/.lvcontainerat clone time..lvcontainerraw text must be imprinted into the job name.Apply VIPC).Acceptance criteria
labview-icon-editor/.lvcontainer..lvcontainertext and derived bitness.Notes
Opened as requested to track this as a dedicated change set rather than mixing into current gate stabilization/merge lane.