Is there a way to suppress the top banner message about NI Package Manager updates? Also is it possible to filter out the NIPM updates from UPDATES tab as well? We are having issues due to people having different versions of NIPM and that causing packages to to be listed in the PACKAGES tab if they build with a newer version the default version of the team.
Solved! Go to Solution.
You can suppress the banner by running the following command from your NIPM installation directory (usually C:\Program Files\National Instruments\NI Package Manager): nipkg.exe remove --force-essential --force-locked ni-package-manager-released-feed. This unregisters the NIPM update feed. Unregistering the feed should also remove the NIPM updates from the Updates tab.
Note that if you upgrade NIPM by other means (perhaps by downloading the installer from the NIPM downloads page), the feed will be registered once again, and the banner will return when updates are available.
Only caveat is that removing the feed will not suppress the too old message if it is present. However, it will render it unable to complete if clicked.
Related to that "too old to handle newer installed software" message, I discussed this with the development team earlier this morning, and we agreed that we should probably have a feature to support suppressing NIPM update functionality. That would prevent both the "too old" and "update NIPM" banners from displaying. We had gotten a request for something like that from an internal team earlier this year as well. I can't speak to when that feature will be prioritized, but we appreciate your engagement here, and it's on our backlog.
Hi Bill, so that I can capture specific rationale for the ask, can you summarize why you or your end-users need the ability to prevent systems from updating NIPM?
The main reason is for consistency/uniformity. It is basically me supporting ~100 user so I am trying to keep things simple. Also, we have run into issues when someone has updated NIPM that their packages are not shown in the NIPM GUI of others who are not. The issue seems to be the version of NIPM installed on the machine building a package, not listing the minimum feature set required.
Bill, thanks. Restricting PM version would be the best option right now. A related consideration that we have is to improve PM internals so that PM does not have to increment its compatibility version almost every release.