GitLab Tanuki Tech, 20 Jan 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: TT310 GitLab Demo (Lukas Mertensmeyer)

Description

Date: 1/20/2022

In this demo, Lukas Mertensmeyer does a brief sales development demo of our product.

A

Okay, great so um now after we had some conversations, um we talked a lot about your tools. I showed some slides, um but obviously I would like to give you a better impression of gitlab as well. So, if you would like to even though I'm not a technical person, I can show you the workflow. A developer would have when working with gitlab. Would that be fine for you great cool? So then, let's directly jump in and yeah. So this is what you would see if you enter gitlab.

A

This is a repository you see here the description um of this project. You see all the files here in this project, maybe with uh with the last commit in the last update right.

A

You can also adhere some kind of readme, and this is the the source code management part of gitlab right and gitlab has the full version, control capabilities, so the history, the commits that were made to this repository, are transparent and traceable.

A

So if you would like to work no on something new right, you would probably open a issue, and um so here at gitlab this would be a list of issues and um let's jump in one of those issues. So in general, what is an issue? An issue is a discrete unit of work for developer, for example, can be also something non-development really ige. Development related right can be something out of the business world, so it gets like. We also manage marketing events with those issues.

A

So um let's look at this issue, so just a name of the issue. We have a unique number for this issue. We you can describe which problems you would like to solve would be the target personas. That would benefit by solving this problem or by adding this functionality.

A

You add some further details. uh You can also um add some. You know designs.

A

Maybe you came up with and um yeah, so you can also include your tasks like to do like check checkboxes and um what I really like is- and this is where the increased operational efficiencies part of gitlab comes in- is that you have here sample space where everyone and really everyone, not just your team, also other teams can collaborate, can discuss those issues, so you bring in maybe also someone from security you bring in people which are not direct developers but maybe assess the impact of this functionality out of a business perspective, so you can have a year the discussion, transparent and traceable.

A

What you also can do um when what you want to do when you open those issues, is, you can add a milestone in our case in my exponential release here, this was 13.5.

A

um Your developers can track the time that they would spend on working on this issue. You can add a due date so until when this issue should be resolved should be closed, you have labels little very important part of gitlab. They monitor your issues. They also control your issues, so you can say which business unit is affected by this, or is it should be included in this discussion in this issue here, in our case, we also say which git lib tier is affected.

A

um Also, you can say which database series you have like backlogged um to do, uh etc exactly, and we also have weights, meaning yeah. How high is the effort that your um or how high is the effort for this issue right? It's good to to make your planning yeah it's good for project management or for the management or leadership in general too? Well, you do work of developers, and so on. You also see the participants.

A

The participants are people that somehow really participate in the discussion in the coding part in changing the description of the issue. Okay, great. So if now, a developer would like to make a change to this issue or, in general, a change a commit to commit code. um They would, in the case of gitlab, open a merge request.

A

So a merge request, um like I said, is a request to change code with a proposal to do it. So this normally, um you would have your the description. Why do you do this? What you do? um The merge requests are normally directly related to an issue. You can close an issue if this merge request is approved so merged, and here again you would have to. You would have some space for discussions also right and um yeah.

A

So here again you see transparent, which changes were made by the way. This is not an a merge request, or this wasn't an issue. I worked on, it's just for me as a um as someone who not worked uh edit, it's transparent, and this is what I really like. So here you see really which code was removed, which code was added? Okay, great. So now the gitlab ci parts comes in right, so you would make a um you would make a proposal and you would like to change code now and the those code changes.

A

The code commits um triggers pipelines and those in this case four pipelines were triggered, and here you see the different stages of those pipelines and you get directly which you are easy to understand feedback. um So you see was the stage past where the jobs in the stage passed and did you had any warnings? Maybe were there any jobs that failed? In this case it looks good right. We have indeed here a test that failed so this year, in this case the test stage failed and um yeah.

A

So I would like to show you more here because I think it's a super important and super strong part of gitlab as well. So this would be the overview of um a gitlab um pipeline.

A

Those are the different stages. You can define the stages. I will explain more in a minute and um yeah, so here, let's look at the test stage, so the test stage can be the quality assurance that can be the security part right. So you have your dependencies getting included you check for the code quality.

A

um You have static analysis uh secrets, so security detection, static application, security, testing, dynamic application, security testing. All this can be done here and um yeah. You would get your uh obviously more overviews uh or or better overview in detail overview if you would needed um of the jobs, maybe of the failed jobs right and here you would see the console output.

A

You may know from from other tools if you want to really have a more detailed, a more detailed overview great so I just mentioned you can define those stages, you can define the jobs and it's actually not that hard to do it at gitlab. So you remember here the different stages right in the different jobs, and you can include jobs, you can remove jobs, you can configure those jobs, um you can even add or remove stages, and this is all done via yaml file.

A

um I think it's easy to understand, so you would define your stages. You would define the image and um yeah some some. Some jobs can be defined in those yaml files and um yeah. So we provide a documentation around that. I think this can be very helpful if you would like to come up with your own pipeline, um but in general those would be the way at gitlab of how to define those pipelines how to configure it and yeah.

A

So this is just a rough overview.

A

Would you have any questions, so I'm happy to answer your questions.