J-Crawler - Automating and Enforcing Code Quality
summary
JKI’s J-Crawler is a LabVIEW static-analysis and automation system that audits repositories, emits console/JUnit-style XML and CSV artifacts, and can apply automatic fixes where safe. It discovers VIs, classes and projects, enforces project-specific rule sets and exemptions, and integrates into Bitbucket CI with a self-hosted Windows runner. A real run processes 4,220 VIs in 8 minutes, flags broken VIs, finds CWE issues like unsafe C execs, and sits alongside jbuilder and jtester to produce NASA‑grade evidence.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:00NASA static analysis needs
- 4:26LabVIEW static analysis gap
- 5:30Static analysis in LabVIEW
- 6:55J-Crawler discovery and rules
- 8:40Automated fixes and customization
- 10:06CI pipeline enforcement
- 10:47NASA compliance rules
- 11:54Metrics and inspection rules
- 13:18Custom rule development
- 17:12Rule configuration and exemptions
- 18:38GCLI integration
- 19:42Bitbucket CI integration
- 20:47CWE security checks
- 21:52J-Builder setup
- 22:55Future development
related talks
39mTrust Issues With UI Automation
44mImproving Software Quality with Jenkins
11mAutomated Code Review for AI Agents
13mContinuous A11y - Automate the Hell Out of It
39mAutomating Your Security Checks: Stop Hiding Your Flaws Next to the Monsters...
30mQA in DevOps: Transformation thru Automation via Jenkins
24mStoic Automation Testing
41mThe Tester’s Guide to Quality