Add build workflow using vipm-io/action-vipm-build#28
Open
jimkring wants to merge 2 commits into
Open
Conversation
New .github/workflows/build-action.yml replicates the refresh -> install -> build steps of the inline container Build job using the reusable vipm-io/action-vipm-build action, which encapsulates the LabVIEW container display/headless plumbing and VIPM install.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new workflow,
.github/workflows/build-action.yml, that builds the VI Package via the reusablevipm-io/action-vipm-buildaction — replicating the important steps of the inline containerBuildjob:vipm refreshvipm install error.dragonvipm build source/.vipbThe action encapsulates the LabVIEW-container plumbing (Xvfb display,
LVContainer.txtmarker, the$HOME/natinstcopy, headless LabVIEW launch) and the VIPM install, so the workflow is just checkout → cache → action → upload artifact.Notes
@mainfor now; switch to@v1once the action cuts a release.previewchannel build26.3.0-3859(VIPM Linux.debs currently ship onpreview).ci.ymlis left untouched, so the inline approach and the action-based approach can be compared side by side.🤖 Generated with Claude Code