 So, good evening everyone. I will talk about our initialization of application build in immediate environment. So, I'm 27 and I'm a new immediate engineer in IOTBZDH. We are 12 IGL full-time developers in application security, continuous integration, and we are the first IGL technical contributor. As you can see with the number of commits, we are located in south of Brittany, in France. So, what is IGL? Automotive Linux is a new Linux system for cars. It's the first collaborative project of the Linux Foundation with more than 110 members, mostly big car builders. It's based on code first model with fast innovation and open source effort. IGL technology is based on IOTBZDH platform and supports any car, any board. You can find yours in the list. Now, the problem here is how to speed up application build process. The link application manually is long, repetitive and very boring. With an exponential matrix of complexity due to number of applications, version system configuration, and hardware The only way is to buy a Chinese army or automatic the build process. Our solution is to keep the build platform, use cross-development system, tool XDS, use automation continuous integration tools as Jenkins, and for the test, we have a combination of Fuego and Lava. So, an overview of XDS cross-development system. It's enable MD development outside Yocto. It use Yocto to build its complexity. With the faster process, the platform and application are not linked each other. So, it allows an easy adoption for any developer. With XDS, we can build for Intel, ARM 32 and 64, with a secure packaging, with a signature on the widget. If you want more details of the internal architecture, we have a schema and you can follow the link below. XDS key features. The XDS client, it's architecture client server. The XDS client supports multi-platform Linux, Windows, Mac OS. It's easy to set up. The application source remain local. And cross-solution and tools are embedded in containers or virtual machine. Now, we can talk about Jenkins continuous integration. It's a self-contained open source automation server, which can be used to automate building, testing, delivering and deploying software. So, Jenkins version 2 brings multiple configurations per task. It has no pipeline. It's the main feature. We can easily look at issues. We have task factorization, easy configuration and maintenance. The Jenkins version 2 pipeline has a powerful set of automation tools. The code is easily editable, iterate and review. It's durable. The pipeline can survive restart of Jenkins. It's possible. It can wait for input. And Versatil, it has the ability to fork and join and perform work in parallel. You can see an example of continuous integration delivery with multiple stage and build and test in parallel. Now, a view of the pipeline with easy location of logs and issues. Jenkins is a plugin who designed for Jenkins pipeline. It will do a fast and intuitive compression of the status and a native integration of punch and pull request. So, our needs for the integration of these two tools, it's to build a four-multi-configuration system, avoid auto-complexity, trigger a job from a repository. Automate building and publish results. Integration architecture. We have a git repository on the top. It trigger a job by a new commit. We had a build box with some magic. And it can publish on different branch with several configuration systems. Inside the magic box, we have three containers in this case. We can also have a NOS machine and two women's server. We have a Jenkins master who talks on his slave, the Jenkins slave. The Jenkins slave have XDS client tools who tell to his pool of server to build the source code. Then the slave takes the result and publish on the server. The Jenkins server. XDS and Jenkins would come. So, Jenkins can automatically trigger and build your code. The pipeline can build in parallel several configuration. And XDS tools can avoid auto-complexity. So, IoT is hiring. If you know anyone, we have six open position and two interships. A little video. We have three containers. The Jenkins server. The Jenkins slave on the top with XDS client tools. And the last we have the Jenkins server. Now we can take a look on the network with a useful command. This network is created by Docker, basically. And it brings an address for any containers. So, we can talk each other. Now you can switch to the Jenkins part. We have a pipeline job with a HVAC HGL code. We have the stages. On the first step, I set up the project ID and the SDK ID. I create the project with the command line XDS and build with the same command line. So, we have to write the process. So, all is good. And we have three widgets with three different configuration system online in the Jenkins server. So, this solution is released online already. You can follow the link. The next step is to take care of the load balancing management of the server and dynamic sizing of the XDS server pool. And also add test and employee stages with Lava and Fugue integration. We have some references. And don't forget IoT Visit Edge is hiring. And that's all for me. If you have any questions, thank you everyone.