Modern Development Workflows in LabVIEW
summary
Practical specifics: uses Git with mainline branching, small frequent commits, and separates compiled code; CI agents run platform‑specific LabVIEW builds with license automation, NIPM/VIPM or JKI Dragon for dependency installs, and artifacts pushed to JFrog Artifactory. PRs include automated VI diff reports (pictures of diagrams), static checks via VI Analyzer or pylabview, unit tests integrated into pipelines, and the 2024 Q3 editor supports a project save version to keep source compatible across LabVIEW releases.
AI-written summary · about
chapters (17)
- 0:00Modern LabVIEW workflows
- 4:14Key workflow elements
- 5:36Setting up developer and build agent machines
- 7:20Containers for LabVIEW builds
- 8:26Source control importance
- 10:14LabVIEW source control best practices
- 11:58Branching models for LabVIEW
- 13:00Code review strategies
- 16:17Managing external dependencies
- 18:02LabVIEW add-ons and versioning
- 20:59Build output locations
- 24:59Static analysis and enforcement
- 27:56Testing and automation
- 29:02LabVIEW CLI tools
- 33:21Documentation in workflow
- 36:42Future guidance and collaboration
- 46:00Q&A Docker and workflow
related talks
56mEverything You Need to Know about VI Scripting in LabVIEW
55mLabVIEW at a Large Scale R&D Facility
21mFighting Git Workflows
37mAutomated Testing and Continuous Integration/Delivery: Lessons Learned
05mSet it and forget it!
27mThe Wonderful World of Rust Tooling
01h 39mMastering git collaboration -A DevOps necessity
56mA Practical Look at NetDevOps