Hi everyone darren eastman here, proud manager for gitlab runner in today's speed, run I'll cover a new model that we've added to the gitlab ui to help simplify the experience of installing a runner to a project or group. This is part of our broader themes of improving usability and also helping users to get to a full screen, build as quickly and effectively as possible.

So the feature in question is issue number two, one, four, five, eight seven, it's titled! I get that running, guided, install view to ci cd settings, so I'm just gonna go pop over and demonstrate this now in one of the systems I have set up, so I'm going to use them coming in. Let's say: they're not shared when it's currently installed in my environment. I've got a project set up. I need to go ahead and get gitlab see I'm going well.

In order to do so, I need to have a runner run into the engine that actually works and make sure that the jobs get the ci jobs gets executed on your gitlab platform, so the user. Coming here to my project, I go into ci cd and expand this, and here you see where we have the runner section.

So then, when I click expand as an end user, we have a couple of different installation instructions, one you can install these the github run directly in kubernetes, but as a first time user that may be too far over the list. You may necessarily be ready to go, install and get going on, kubernetes yet and then right below. We have installation instructions, just go ahead and get us around going on an environment. Maybe your local macintosh show you another machine, or what have you because today, without installing experience of installing the lab runner here?

What our install experiences actually takes, you out of the ui and into the docs page, and that's fine, but we when it goes out to the docs page, there's a little information on that page. A little about content and so on, so it's taking the user out of that experience, and so now what we've added with this new feature is the showrunner installation instructions button here, which one demonstrates right now which will bring up this model. This new install motor basically proves presenting on bringing that install experience directly into the ui.

So you see as if I clicked on a button. I now have linux mac or spin those document communities as options for me in terms of getting boring with installing the runner. So please, let me see, let's take a quick look. If I'm on linux, I can choose amd64, I can choose different architectures and what happens is I should makes, as I make those selection choices.

It's giving me right here in the model and the installation, instructions that I need. So it's giving me the commands to where, where I need to run in order to download the on the binary, the permissions to execute the user command the command to create the user. The commands for installing the owner as well and what's also interesting and and simplified from an end user perspective, is that the registrations commands are also displayed directly right here in the ui, along with the registration token, that's needed to associate that runner back to the project.

So we have the environment. Here is working for legs. We have different architectures and the installation instructions changing based on the architecture choice. I can go over to mac os right now for mac os. I think we only have actually. I know we only have empty. 64S architecture still will iterate on that in the future release, um then windows we've got the md64 3sx now for dockers and kubernetes.

When you click over to dark or you click over to the computers option, the actual install instructions are not yet in the model we'll iterate on this in future, uh in future versions of of of this feature, and so for those environment for those platforms of those targets, if you will, uh it will take you out to the installation instructions.

So that's it. That's the new model feature that we've added and the idea being that we wanted to build on this feature, to add additional automation, to continue to simplify the setup and configuration experience again, the end goal being to improve usability and- and secondly- and it's just as important to ensure that we're helping users get to a full screen bill as fast as fast as possible. So that's it for today's speed run and check you next time cheers.