 One of the questions and this is one that we get frequently and it sounds like the question is can you Can you adapt or modify the auto DevOps pipeline and the answer is absolutely yes And so when we chat about this we often hear things like That's great that you have auto DevOps in it and it spun up a pipeline for me automatically But how about being able to then export that auto DevOps into let's say a git lab see a YAML file and The answer is get lab works a little bit differently than that. So rather than having Some functionality that you configure via pointing and clicking on things and then exporting that into some type of consumable format GitLab actually does it the opposite way around our auto DevOps functionality is based on predefined code And if you want to modify that code, you can simply go to it. So for example Here's a project where I have auto DevOps set up here are some of the pipelines that you can see that are running and The way auto DevOps works is if there's no file and the file is called GitLab CI YAML If there's no YAML file, then it will use the default file But if you put in your own CI YAML file, then it will process that it works the same way with let's say a Docker file If there's no Docker file, it will use the defaults It uses something called Heroku ish to go and detect the language and figure out what types of containers are needed But if either there's not a container there, let's say you wanted to have a Custom definition for your Docker file. You can actually put in that and then auto DevOps will use the one in your repository So I'll show you what the CI YAML file looks like if we were to go to add a new file We can choose via template And for the dot GitLab dash CI YAML file, you can actually choose several different types of templates for different programming languages There are many templates here, but what I want to show you is the auto DevOps template And so this is actually the code that's executing for those pipelines that you saw Dan showing you And I could add this file, but instead since I already have it here I am going to head on back and just open it up here Where we can see it with a little bit of syntax highlighting whatnot So here is the syntax and the file that shows you you can see that there are several stages that are set up And even some that we didn't look at in the demo such as incremental rollout and whatnot So this is not too long of a file. Maybe about I think it's around a thousand lines And you can see all of the scripting and all of the the YAML code That is I should say YAML definitions of the the pipeline here So this is fully customizable. You can start with that auto DevOps that basically gets you up and going with zero work And then when you have that pipeline going, let's say you want to modify something or add to it You can easily add this file. You have the exact same pipeline and then start modifying it Or for that matter, you can use this file as inspiration or templates or snippets to plug into another custom ci YAML file So Let's see if we have some other questions here Another question that we often get will be How does Git labs pipelines compare to say a product like Jenkins or some of the other ci products on the market So in a nutshell, I can direct you to A few places here. So on our home page We do have a comparison section where we look at various DevOps tools in the DevOps landscape. So Across the entire DevOps lifecycle There are a whole array of tools and you can compare various tools To Git labs. So for example, if we were to look at let's say Jenkins, how does it compare? There's some more in depth info here and I direct you to this resource But in a nutshell There are some a few key differences to Jenkins in particular and then to other ci tools in general So Jenkins in particular is really not one product, but it's it's really three different products Historically, there's traditional Jenkins that was not built in a in a cloud native era to take into consideration things like cloud infrastructure micro services serverless containers, etc And that traditional Jenkins has a bunch of plugins. That's the one that's the most popular There's also problems with it though and that all of those plugins Whenever you want to upgrade your instance, you have to then go and upgrade all of those plugins. They're often Community managed the plugins break. It was in fact our co-founder The pain of him having to upgrade his Jenkins instance Is why he decided to build his own ci. So that was the impetus for gilab ci Of course, then there's other modern versions of Jenkins such as Jenkins x that do take into consideration things like kubernetes And containers for git lab. We don't have separate products For separate things and there's no choice for you having to decide which one you can use Git lab by itself just supports kubernetes regular git lab vanilla git lab ci is a modern tool Based on all of the modern technologies such as containers and kubernetes That's just built in and we integrate with those things And we're really I believe on the on the forefront of that space and driving more technology So gilab's not just a great product for you today It's one that we will partner with you and be a great product for you in the future the last way that really gilab is different is that gilab ci is built in and integrated as part of the whole flow So as you saw in the demo in the merge request You see the output of your pipeline and you can dig into every single part of it And you can even modify the pipeline right from the code repo for example by editing this file That exists right inside of the repository And so this gives developers a sense of self control or self service and control That allows them to collaborate together with operations teams And we have some advanced functionality that we didn't show today around Templating importing allowing you to have parts of your pipeline that are stock and based on your operations team And then the developers can import that and then extend and modify it So there are lots of controls to put in there But in the nutshell by allowing developers and operators to communicate and collaborate together in one interface Is something pretty unique to git lab Whereas using any other type of ci or cd tool you need to integrate it with a bunch of different tool chains. So Let's take a look. It looks like we have a few words in chat here and What I'll do is I will talk about one more question which is pricing And it looks like you can go to our homepage about dot git lab dot com And if you check out the pricing link One of the things I'll point out is you can get git lab as either git lab dot com hosted on the cloud where We actually manage that instance and we do all the administration So you simply sign up for it as a SaaS service Or you can download and install git lab yourself as a self managed instance And of course you can run that on your on-premises hardware You can run that in gcp azure aws whatever cloud or Public or private cloud you wanted to run that in And our self managed and our dot com actually have the same pricing model So some of the features you saw such as our security features are in our top tier plan and Basically, we also have a free or an open source plan That allows you to get started right away and you can look at a full set of which features are in which plan on this comparison page where It has a familiar check box feature style page there so With that it looks like we don't have any other questions coming in So I do want to thank everyone for being on the call today We will of course send you a follow-up email with a link to the demo video and these questions And if you have any more, please do respond to that email and reach out to our team We'd love to continue the conversation with you With that, uh, thank you everyone. Please do have a wonderful day. Cheers