 שלום, אני אמצע גנברוך ואני רוצה להסתכל על קצת האפריביטים שיאמצעים פרופות קצת. To maximize development time and improve team productivity, you will need a tool that will allow you to automate everything or almost everything you do. In addition, this tool must be easy enough to configure, so you will focus most of your time on developing and less on configuring the tool and maintaining it. A great tool will allow you to make the configuration via the web UI with a few steps and will make the automation for you. In case that some customizations are required, the tool will support configures code in a human-readable syntax like YAML. Let me show you an example of how I configure my build and test automation with a few clicks in the web UI. This is a GitLab project. I've just pushed my Java code to its repository. Now I want to set up a continuous integration pipeline or in other words, I wish that for each code commit pushed to this repository, it will automatically be built and tested. I'm lucky because in GitLab I have to do nothing to set it. I just have to enable it via the web UI. I will click enable auto-devops. It opens the settings page. I will enable this setting and save changes. Now I'm ready to run my pipeline. A new continuous integration pipeline just started. It will build and test my code and even push it to the container registry, so it will be ready to be deployed to test our production environments. But what if I have to customize the configuration, for example, and remove some automation jobs? How can I make this customization? Editing the CI configuration is done in a YAML file. This file is part of your repository and you can edit it with any editor and commit the changes like it was any file in your code. I will use the web ID to create this file. Choose the file type and apply the appropriate template. In this case, I will select the auto-devops template. Now I can make changes to the configuration. I will add a new job in the build stage. The job will run three scripts. In this case, it will run echo. But you can call any script. I will commit this change. A new pipeline will be triggered immediately. And we can see the new job we added appears here. Clicking it will present an online status of the job. In case I have to use passwords or secret keys in my jobs, I can define those keys as parameters via the web UI. Once the parameter is added, I can call it in the YAML file. This keeps my YAML file secured. As we have just seen, with the right tool that does the hard work for you, dev teams can focus on their applications instead of configurations. Thanks for watching it.