 Good morning, Berlin Today I want to talk about why we at BMW or BMW how we pronounce that in German are using Zul for driving our continuous integration of our future automotive projects So first of all, I want to outline a bit of the history in automotive software development So we can see where we're coming from and where we're heading to so in the beginning there were all only a few small electronic control units in the car that can contain small portions of software and Still while these were small they still had to fulfill Higher safety requirements. So what is extremely important is automatic testing in the software development process also back in that time While these projects were still small also small the ISIS systems were sufficient So a typical setup for example would be Jenkins with a few build slaves so later the existing features evolved and many new complex features were introduced and Then out of software became an enabler in for new features like for example Advanced driver assistance features and That's also the code sizes and the complexity of the software increased also, this means that the number of the ECU's in the car increased also and With that we had a higher demand on Continuous integration systems. So we had we grew more CI systems and still the typical setup for that was a Jenkins setup with a number of build slaves depending on the size of the project So the software that is running now in the car is even more complex So software now is everywhere in the car Ranging from the window lifters up to the most complex infotainment systems And that means that we have much more code and much higher complexity of the software to handle further This also needs to that we have many internal and external teams developing the software And this is going to be it. This is a chat lunch Also to organize and drive the development process. So what is crucial for this is that we not just need automated testing for ensuring the software quality, but also we need automation for running the software development process itself for for example creating and delivering releases and so also the Requirements for the CI systems increased a lot A typical tank a setup for it is for for example Jenkins multi master setup with many build slaves But we are also an early adopter of Zool of using Zool outside of the open-stack Ecosystem so for certain smaller projects. We already started more than four years ago to use Zool on our private cloud And we also were among the first users that switched to Zool v3 even before it was released so now we are developing the software of the future cars and for this we have to drive many huge projects in parallel This also requires cooperation of many International teams and suppliers And this also covers on-board software as well as off-board software Just one example is autonomous driving. So the development of autonomous driving is a huge effort and also requires very complex software stack and this will going to be One of the largest challenges in the automotive software development Since the beginning So Also safety and security is obviously one of the most important things With these kinds of projects and thus we also need an excessive amount of simulation So for example, it is not not not sufficient to just run unit tests system tests and Manual test rise, but we need to simulate millions and millions of kilometers to ensure that also we have enough testing Done Running the CI system for such kind of projects is extremely challenging And so we have a large need of a large-scale CI system And we chose to do that to drive that so it's already in use by several larger projects and by international development teams and partners and one of The features that are most important to us is that school scales horizontally with its resources So while the while our projects grow we can add more cloud resources to the CI system and then can Technically scale the CI system to to fulfill more the requirements for more developers But in my eyes as a software developer, this is not the most important feature of school. The most important feature of school is like Monty also said the Automatic gating feature functionality of school. So I think this is key. This is the key to not just scale the available computing resources, but also to scale the development teams themselves. So Consider without gating when the development teams grow. So there's a widespread Process of stop and fix if if the build is is not working if the build is red When the teams grows that Is going to be a major problem for the scalability of the teams And I've seen many projects larger projects that then tend to just Merge their new features to get their features done quickly But then that would require having regular Fix the build days or even weeks and that is going to be a problem So with the automated gating of school you can prevent fixing breaking the build up front and so This can dramatically improve the software development process itself and further Zool is a great open-source project and with a very helpful community and we are very proud of Being an active member of that. So If you're interested in hearing more about how we run school at BMW Then join us at the breakout session later today at 140 Thank you very much