Some cars today boast more than 300M lines of code! Software has become a key differentiator and influencer on consumers’ buying decisions – with many choosing vehicles as much for their infotainment system and “all that tech” as for the horsepower. DevOps for software embedded in vehicles is not trivial. The automotive industry faces unique challenges when it comes to delivering software — due to complex testing matrix and deployment processes, and its strict safety, regulation and compliance rules.
DevOps and CI/CD automation enable automotive manufacturers to accelerate their releases while ensuring security and mitigating the risk of failed/recalled software releases.
In this webinar you will learn:
- How DevOps helps solve the challenges around Automotive and Embedded software delivery
- What a modern CI/CD pipeline and toolset look like in the Automotive industry
- DevSecOps best practices: How to ensure security and compliance as an integral part of your pipeline
- Patterns for reducing the footprint/latency of last-mile deployments to speed-up releases and minimize service interruption
- Hard-won tips and tricks around increasing developer productivity and collaboration for complex embedded software, including:
- Typical Pipeline Workflow
- Quality Gates and Compliance
- Observability of deployed versions
- Last-mile deployments
Who should attend: DevOps engineers, Software developers and managers from the Automotive industry.
Pre-requisites: Basic understanding of DevOps
Following the webinar, these great questions were asked by the audience and might be of interest to you.
There is no real limit on the number of edge nodes. However, the typical solutions/topologies we currently encounter, is to have edge nodes not in the car, but a near geo location (e.g., regional, service centers, etc…). Decision on edge nodes for solving ‘last-mile’ problems should best be discussed on a per-use basis. Edge nodes will be updated when going online, unless the defined timeout for the distribution has reached.
YAML files that can be divided as you wish (for modularity). We recommend having the CI related parts in the respective projects being built and the CD parts in a dedicated git. However, very flexible and you can restructure anyway you want. We also support integration with Jenkins so you don’t need to throw away existing efforts. You essentially define (by regex) where are your YAML files for the pipelines.
B/G deployment are fully supported as we can have multiple repositories on the edge node. Then we can promote from one repo to the other instantly
Definitely. However the process must be configured to use it as the runtime component should be set with a basic logic of leveraging the B/G repositories. You can also leverage our support for virtual repositories to essentially change the resolution order of the underlying repositories.
A Release Bundle version can include up to 3,000 artifacts. This number is not limited in the product, but exceeding it is highly unrecommended.
Hi Pablo, thank you for your question. Bintray commercial offering is going down by the end of the year. Another solution to distributing your artifacts can be preformed by Distribution and allowing your customers to access the edge nodes.
No, it's only possible for distribution. For more information about Artifactory Edge Nodes: https://www.jfrog.com/confluence/display/JFROG/JFrog Artifactory Edge.
You can use JFrog Bintray - a cloud platform that gives you full control over how you publish, store, promote and distribute software.