GitLab held a Lunch & Learn on January 15th about Embedded DevSecOps: The Power of Automation and Collaborative Engineering.
GitLab, Blue Ivy Partners & Carahsoft explored how DevSecOps principles can revolutionize embedded systems.
During this session, GitLab tackled a few core concepts, outlined below, designed to optimize your development pipeline:
- The Transformative Power of Collaboration and Shared Process: Discover how moving from isolated development to a collaborative, sharing model can accelerate innovation. This shift helps you:
- Accelerate skill development and foster innovation through shared knowledge
- Improve workflow automation and enhance security by integrating policy checks into your processes
- Gain shared visibility into the mission value your work create
- Demo: What GitLab Does for Embedded Today - like a public cloud, GitLab has a lot of composable DevOps pieces that can service Embedded workflows today
- Hardware and Software in the CI Loop: Learn how to move past development bottlenecks by integrating real hardware into your Continuous Integration (CI) process. This approach helps you:
- Reduce bottlenecks and increase hardware utilization by running tests around the clock
- Reduce costs by offloading testing to more scalable, simulated environments
- How DUO AI offloads cognitive load when adopting Agile, DevOps and rapid iteration
- Enabling DUO with Embedded Stack Expertise for each project
- Continuously Compliant and Traceable Firmware Release: Learn how GitLab serves as the secure foundation for your software factory with:
- Full traceability of firmware from field devices to precise CI jobs and even individuals
- Attested Software Supply Chain Security through GitLab's SLSA manifests
- Binding Identifiers To Software Release with a Chain of Custody - the example shows UN R156 (automotive) - but easily applies to MIL-STD-130, MIL-STD-498 and traceability requirements of DO-178C
- Avoiding Storing Released Firmware in Git - alternatives that have many more features, portability and do not bloat Git with binary content