Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 09/17/2019 in Posts

  1. 1 point
    Reading the above thread, does this mean that the Linux VIPM 2017 will only work on LabVIEW 2017 and not 2018 or 2019? If so, when does JKI anticipate a release of VIPM for Linux that supports newer versions of LabVIEW? Respectfully, David
  2. 1 point
    Yes, you can have Jenkins run a set of tests for each commit. You might want to try using the G-CLI tool to run a set of VI Tester tests from the command line. It was created by @jamesmc86 and it's a great tool (we even use it in the build process for JKI Design Palette)!
  3. 1 point
    Hello, I am trying to determine if this would be suitable for Continuous Integration, i.e. run Test suites after each commit. Ideally Jenkins would call the executable which calls the JUnit plugin (https://github.com/JKISoftware/JKI-VI-Tester-JUnit-XML-Test-Results) After testing Jenkins could evaluate the output file generated by the exe. I can create a Test Case and can use the JUnit plugin to load it and generate a report. However if I try to replicate this in an executable I get error 1448 even though the library is not broken. I tried including my Test case into a PPL but there was no difference. More compactly my question is as follows: Is it possible to integrate this with Jenkins and run a set of tests for each commit automatically?
  4. 1 point
    Hi Jim Thanks for the quick reply. Based on this information we decided to keep the current blue color. Again, thanks. Sebastian
  5. 1 point
    Hi Sebastian. I'm pretty sure the only way to change this is by tweaking the menu color settings in Windows. So, if your customer is willing to do that for all Windows applications, then that could be a good solution. There are some other LabVIEW users who have discussed this here: https://forums.ni.com/t5/LabVIEW/ring-selection-label-appearance-customization/m-p/3259968#M950846 I wish I had a better solution for you. Maybe someone else can think of one.
  6. 1 point
    Hi Helcio, Yes, this happened in 2018. Our official statement about this is included in the release notes: "In order to best support our customers and ensure LabVIEW compatibility, VIPM supports new versions of LabVIEW as they are released. There are many instances where older versions of VIPM do not work well with newer versions of LabVIEW, due to changes in where/how LabVIEW and its files get installed." JKI has to provide support for each new version of LabVIEW as it's released, so we needed to align our support and releases with LabVIEW.
  7. 1 point
    Hello Jim, It used to be that older versions of VIPM could connect to the newest versions of LABVIEW. Is there any particular reason why this changed? This issue seems to have happened from the VIPM 2018 Version because it was a major update. Is this going to happen for all versions of VIPMs in the future? The problem is that I have a licence for VIPM 2018, and now I can't use VIPM 2018 with LABVIEW 2019 (I won't be able to generate VIPC files without the licence). thanks Helcio
  8. 1 point
    Hi Helcio, Yes, you will need to use VIPM 2019 in order to manage LabVIEW 2019. You can upgrade via the menu in VIPM (Help >> Check for VIPM Updates) or download from vipm.jki.net/download -Jim
  9. 1 point
    It would be nice if we could re-install a specific package. I had some crosslinking between 8.6 and 8.5 (my fault) so I wanted to revert a package. This couldn't be done, so I had to install an older version of the package and sequentially install the newest version. Ton
  10. 1 point
    Hi Ton, That's a great idea -- we've noticed that we need that feature, too. It's on our roadmap. Thanks, -Jim
×
×
  • Create New...

Important Information

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