Include ni-grpc-device.conf.yml and ni-grpc-device.caps.yml in Linux RT tarball#1255
Open
texasaggie97 wants to merge 1 commit intoni:mainfrom
Open
Include ni-grpc-device.conf.yml and ni-grpc-device.caps.yml in Linux RT tarball#1255texasaggie97 wants to merge 1 commit intoni:mainfrom
texasaggie97 wants to merge 1 commit intoni:mainfrom
Conversation
astarche
approved these changes
Apr 1, 2026
reckenro
approved these changes
Apr 1, 2026
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
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.
What does this Pull Request accomplish?
Adds
ni-grpc-device.conf.ymlandni-grpc-device.caps.ymlto the "Tar Server Build Files"step in
build_nilrt.yml. Both files are now included in theni-grpc-device-server-ni-linux-rt-x64.tar.gzartifact alongside the existingserver_config.jsonandserver_capabilities.json.Why should this Pull Request be merged?
These TLS config files were added in a previous PR but were missing from the Linux RT
tarball. The CMake build already copies both files from
source/config/to the binaryoutput directory for all targets (including the NILRT cross-compile), so they are present
in
$GITHUB_WORKSPACE/build/at packaging time — they simply weren't included in thetarcommand.Without this fix, users installing from the Linux RT tarball would not receive the default
TLS configuration files needed by the server.
What testing has been done?
This change is a one-line workflow addition to an existing
tarcommand. Coverage isprovided by the CI pipeline: the
build_nilrt.ymlworkflow will produce the tarball andthe artifact contents can be verified to include both
.ymlfiles.