LabVIEW Build Tools

Overview

This extension give you the capability to :

• Run the Caraya unit tests belonging to the project
• Build a LabVIEW executable
• Build a LabVIEW package, publish it onto the server and tag it.

Everything is configured in the LabVIEW project itself.

Example

Agent job tasks

LabVIEW version

This task selects the LabVIEW version used for subsequent builds. This task clears the LabVIEW cache.

Run the Caraya Unit Tests

The unit test belonging to the project will be run with this task.

Publish Test Results

The unit tests generated in the previous step are published onto the Azure Devops Server.

Build executable

This task builds the LabVIEW executable. There is no need to do something particular in the project. e.g. no pre-build actions. This step is executed only if the unit tests are successful.

Build NI package

This task builds the NI package and publish it to a NI feed. This step is executed only if the unit tests are successful. The sources files used to build this package will be tagged on the git server if successful

Prerequisites

• Windows / Hosted agent.
• LabVIEW must be be installed on the agent (with LabVIEW CLI).
• git must be installed on the agent.
• g-cli must be installed on the agent (see Figure 2).
• g-cli build specification (see Figure 2)
• Repository must be VSTS Git.
• Project Collection Build Service must have Contribute & Create Tag set to Allow or Inherit Allow for that particular repository
• Allow scripts to access Oauth must be Enabled Select this check box in classic build pipelines if you want to enable your script to use the build pipeline OAuth token. This check box is located under the "additional settings" section after selecting the agent job in the pipeline In yaml - add a checkout section with persistCredentials set to true.

License

This extension is licensed under the ISC License. See the LICENSE file for more details.