Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 02/06/2021 in all areas

  1. Great idea, Joerg. This is not currently a feature, but it's worth considering, for sure. Your use case sounds valid.
    1 point
  2. Hey JKI team, is it possible to programmatically update an existing .vipc (or, alternatively, create a new one) with a given .vip file? Our use is case is the following: After building a .vip automatically, we'd like to install it to the very system it was built on automatically. Seeing as we already have a tool to apply .vipc files through the VIPM API, and as we could use it "as-is" for this, we'd prefer to install the .vip this way. Thanks for the great tool, Jörg
    1 point
  3. With VIPM 2020.3 (build 2540) and VIPM API 2020.0.2.73, it's not possible to supply a major number of 0 via the API, the API returns an error 42: Seeing as we also build projects that are in a pre-v1.0 state, I don't see a reason to not allow the major build number to be 0. I was actually tempted to file a bug report... 😉
    1 point
  4. Thanks for the clarification on your use case -- it's very helpful (and exciting) to see the code in action that does the automated builds of your VI Packages! We've done some work on a fix for this issue (we're calling it a "bug") and I'll ping you off-line so you can test it out, if you'd like.
    1 point
  5. Jim, as always, your elaboration is spot on. Here's a screenshot of what our tools do: So other than the fact that we write all the build numbers in one go (the whole cluster), it's what you described above. Thanks for taking the suggestion into consideration.
    1 point
  6. Main package list.. i noticed there is update available will see how that goes after update. Thanks..
    1 point
  7. Hi guys, I've written this small wrapper for Run Tests Programmatically which I can just drop in any of our projects, it will find the uni tests in the folder structure and run them. It works perfectly except there is no way to change the result format of the test results. This wrapper also drops the results into the repo so they will be part of the commit/pull request and easy for the reviewer to see. The text result format would be easier to see in Azure DevOps than XML. Is there a way to change the result format for this vi (other than hack it with vi server)? It seems to be
    1 point
  8. Here was last answer from IT which solved my problem : Maybe our problem is not AV itself but something else… I just put this machine xx.xx.xx.xx under a policy that has only AV enabled.
    1 point
  9. Hello @Sam Grayson and @Jim Kring, the IT departement tried to whitelist any folders but it didn't work finally. it was working few time if VIPM start before Cyberreason. Anyway IT solved the issue with puting my computer in a special group to only use antivirus of cyberreason. Now it works correctly. I try to get more information from IT departement and let you know when I have news.
    1 point
  10. For keeping track of used packages for our projects we'd like to put a list of used packages to our measuring data. That way we could later on see if a specific problem we encounter with our measurements might be due to the used packages. Is there an easy way for this? The best way I can think of right now is saving the names of installed packages out of VIPMs program data folder.
    1 point
  11. How to use VI Package Configurations (VIPC) – VIPM
    1 point
  12. Fantastic! Glad to hear you're up and running.
    1 point
  13. 1 point
  14. Release notes are written in the build specification. When, for example, developer realizes that some note should be added - package has to be rebuilt. But sometimes build of the package could take a lot of time (for example, build of our DBT toolkit takes approx. 1 hour with licensing, password protecting and further build). It would be great if there will be option to update just release notes, or another information which should not be compiled (authors list, etc.). That would help to save some time... But on the other side, developer should pay some more attention to build configurat
    1 point
  15. We use G-CLI to execute our CI tools, so we'd write back to G-CLI (and also to the front panel of the tool in case we run it manually). So the point would be to get the progress information back into the VI that's actually using the VIPM API. vipb.mov
    1 point
  16. Building a VI package can take quite a while. For our Release Automation Tools, it takes about 20 minutes. Even though we build our packages on the build server now, it would be great to be able to feed back the progress of the build process to the CI system. As an example, the NI Application Builder API offers "progress bar" events, which you can register for and then show the progress details as you see fit: The VI Package Builder shows at least a few pieces of progress information in its status bar. Maybe these could be "routed" back to the VIPM API?
    1 point
  17. @Sam Taggart, @StefanLemmens. We just published a new build of the VIPM API which should address this issue. https://www.vipm.io/package/jki_lib_vipm_api/#2020.0.0.65 2020.0.0.65 (Nov 17, 2020) This release adds support for VIPM 2020 (including Community Edition) and LabVIEW 2020, and also adds a few new features, changes and fixes: - [NEW] VIPM 2020 and Community Edition support (Community Edition can use API calls, just like Pro) - [NEW] LabVIEW 2020 support (fixes an issue where passing version 20.0 was failing a version check) - [CHANG
    1 point
  18. Some advanced users are asking for support to install VIPM for Windows onto a Docker container. This would allow creating fully automated build processes that spin up virtual machines that have LabVIEW and VIPM installed on them, so that VI Packages can be created automatically.
    1 point
  19. Hello LV Gurus, I have used JSM since release 1.0 (circa LV 2011). I understand the sub-diagram label feature was not yet implemented. Is there a reason why the JSM 2018 still not using sub-diagram labels (like below) since that has been standard in LV for many many years. Thanks guys! Sub-Diagram Labels enabled (lots of manual editing just to clean up those comments) Sub-Diagram Labels not enabled (current 2018 version):
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.