Skip to content

Vipc to toml (This is a Test PR) - #545

Open
Amruthasinchanag wants to merge 5 commits into
ni:developfrom
Amruthasinchanag:vipc-to-toml
Open

Amruthasinchanag wants to merge 5 commits into
ni:developfrom
Amruthasinchanag:vipc-to-toml

Conversation

@Amruthasinchanag

@Amruthasinchanag Amruthasinchanag commented Sep 4, 2026

Copy link
Copy Markdown

GitHub Issue for the Pull Request

N/A

GitHub Discussions Related to this Pull Request

N/A

Checklists

  • I do not require assistance from NI to complete any of the following checks.
  • The changes in this PR are based on the appropriate NI-repo feature branch.
  • I am submitting the changes in this PR to the appropriate NI-repo feature branch.
  • I built a VI Package using the Powershell build tool.
  • I installed the VI Package produced by the Powershell build tool and tested my change.
  • I tested my changes after installing the VI package.
  • NI has my contributor license agreement.

Summary of Changes

This PR introduces a proof-of-concept migration from VIPC-based dependency installation to a vipm.toml manifest.

Changes included:

  • Added a vipm.toml manifest containing the runner dependency definitions previously stored in the VIPC.
  • Updated ApplyVIPC.ps1 to install dependencies using the VIPM CLI.
  • Added VIPM lock generation and validation support.
  • Updated action.yml to use the TOML-based workflow.
  • Updated Run-CICompositeLocal.ps1 to use the TOML manifest.

Reason for Change

While investigating dependency updates, it became clear that updating and maintaining dependencies through VIPC files is difficult. After discussion with Navneet, we explored a TOML-based dependency management workflow using the VIPM CLI.

This proof of concept evaluates whether runner dependencies can be managed through a source-controlled vipm.toml file instead of a binary VIPC file.

Visual Aids

N/A

Additional Information

  • Existing LabVIEW version selection behavior is preserved.
  • Existing 32-bit and 64-bit support is preserved.
  • CI uses VIPM lock generation/validation for reproducibility.
  • Local environments can continue installing directly from vipm.toml without requiring lock generation support.

Testing

Manual Tests

@elijah286

Copy link
Copy Markdown
Collaborator

I challenge that we absolutely should be using VIPC files, as that is the convention used by our customers and by industry. I'm not familiar with TOML but would caution against a different paradigm that is not well-known to our user base.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants