papowerNI
commented
1 year ago Note: this is failing temporarily because Azure Pipelines triggered the LabVIEW 2023 build before its dependency had finished, and since the archive location has changed, no data existed yet. This will be a perfect opportunity to test Rerun Job behavior.
Edit:
In image above, ".finished" is not placed when 1 job fails, but as shown in the image below, it is placed when you use Rerun to rerun the job without kicking off a whole new pipeline:
What does this Pull Request accomplish?
Adds an azure-pipeline.yml that runs using the pipeline templates from custom device build tools repo. Currently the build artifacts are targeted to \daqserver\temp\papower to avoid interfering with the nirvana archival from jenkins.
Why should this Pull Request be merged?
This custom device exercises most of the complex behavior in custom device building, including multiple payload maps in multiple nipkgs, multiple projects with varied build specifications, and multiple dependencies. It depends on niveristand-routing-and-faulting-message-library which has a PR also posted here.
What testing has been done?
Ran the build before posting the PR, but the builds should also link at the base of this PR.