You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The download-rio-image script is pretty gross. One way to clean it up might be to simply run CI on windows and use the actual NI package manager to install the utilities package.
The text was updated successfully, but these errors were encountered:
On Sun, Dec 22, 2019, 03:22 David Vo ***@***.***> wrote:
Does the NI package manager even run headless?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2?email_source=notifications&email_token=AALRH2SVLZCXXC4GCD4VFUDQZ5EVRA5CNFSM4J6LJZVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHPNW7Q#issuecomment-568253310>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALRH2RLKYEK322CKNMQMGDQZ5EVRANCNFSM4J6LJZVA>
.
Shipit! Thanks for doing this. The only nit is have is that the roboRIO_*.zip files are left in the working dir which inflates the docker build context a bit during CI, but it hardly matters imo.
The download-rio-image script is pretty gross. One way to clean it up might be to simply run CI on windows and use the actual NI package manager to install the utilities package.
The text was updated successfully, but these errors were encountered: