Joerg Hampel

For one of our customer projects, upgrading from v1.0.2 to v1.1.0 resulted in an error when trying to build an executable from the project (downgrading to v1.0.2 fixed the build): I understand that we need to tidy our customer's project, having Caraya dependencies in the build is not what we want. The reason I'm posting here is that I'd be interested in understanding why this VI would break the build. Thanks, Joerg

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

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?