Continuous integration w/gitLab not working after updating Labview version

[kchang408]

There was an ABCD tool with a Gitlab Runner setup so we can do continuous integration.  Whenever we push a code up to Gitlab, it would run the runner and run the ABCD tool to detect broken VI and Teststand seq.  This is not working as soon as we push a code that's LabVIEW 2019 and above and TestSTand seq 2019 and above.  Used to work fine with 2019 Labview codes.  Need help from LabVIEW to provide a tool to work with newer LabVIEW versions.  Now the broken code VI is showing blank and didn't run properly.

[cordm]

What LabVIEW version is the runner using? If it is LV 2019 it won't open files saved with a later version.

The solution is to either revert or save for previous version the VIs that were saved in newer LV version or upgrade LV on the runner (and change the path to the exe in the scripts).

[kchang408]

I have tried modifying the .bat files to point to Labview 2020 and 2022. both didn't work out.  My VI codes being analyzed is saved under Labview 2020. Those don't work either.

[cordm]

I'm not that well versed in Gitlab CI, but doesn't the CI script just call CI-ABCD-Tool.bat, which in turn executes Copy_To_LVData.vi? Does it work as expected if you execute it on your machine?

Maybe the folks in the continuous integration group can be of more help.