Skip to content

Setup a basic CI pipeline for Actor Framework#162

Merged
watsnav merged 8 commits into
ni:developfrom
KSharma-NI:users/krishsha/ci
Apr 7, 2026
Merged

Setup a basic CI pipeline for Actor Framework#162
watsnav merged 8 commits into
ni:developfrom
KSharma-NI:users/krishsha/ci

Conversation

@KSharma-NI
Copy link
Copy Markdown
Contributor

GitHub Issue for the Pull Request

#73

GitHub Discussions Related to this Pull Request

N/A

Checklists

Completing these checklists ensures that your PR meets our build server requirements on the first attempt. If you're unable to complete any of the following checks, please submit your PR as a draft to the best of your ability. We will provide any clarification you may need after posting it.

  • 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 creates a CI pipeline that does the following:

  1. Run VI Analyzer
  2. Create distribution artifact
  3. It then copies the files from the artifact to the correct location in a windows docker container and mass compiles the Actor Framework folder to verify if all VIs are good.

Reason for Change

Currently ActorFramework does not have a CI pipeline which runs on PRs. So, this PR aims to create a basic CI pipeline.

Testing

Tested the CI pipeline in a fork of Actor Framework: https://github.com/KSharma-NI/actor-framework/actions/runs/24039481478

@KSharma-NI KSharma-NI changed the title Users/krishsha/ci Setup a basic CI pipeline for Actor Framework Apr 7, 2026
@watsnav watsnav merged commit 960d6f6 into ni:develop Apr 7, 2026
3 of 4 checks passed
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