Building the Software-Defined Vehicle
summary
Tata Motors describes a live pipeline that links developer commits to over‑the‑air vehicle updates using JFrog Artifactory as the single source of truth, JFrog security for automated scanning and attestation, and PLM/OTA integration for deployment. The platform enforces least‑privilege access and SUMS‑aligned traceability, supports cross‑border collaboration, and already onboarded 15 vendors to the governed repository. The claim: auditable, compliant binaries move from CI/CD to cars in the driveway, and the setup is running in production.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 1:41Software-defined vehicles explained
- 2:43Speed vs trust in automotive software
- 3:49JFrog as the critical delivery layer
- 5:17Security and compliance for suppliers
- 6:40Vendor collaboration and governance
- 8:05Regulations and lifecycle management
- 8:46End-to-end software delivery flow
- 9:51Key takeaways and conclusion
related talks
46mRevolutionizing Automotive Software: DevSecOps, Functional Safety, and Open Source Sy...
36mJFrog Platform Innovation: Reloading Development Teams
07mJFrog Sponsored Session - Narasimha Pai, JFrog
34mJourney towards a software-driven company
30mSoftware-Defined Vehicles and FOSS
29mTrusted Software Supply Chain with JTE
19mDriving Automotive with Open Source: From Compliance to Collaboration
25mData Collection and IoT for Vehicles in Practice