GitLab GitLab for Education Videos, 19 Apr 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Learn GitLab with Pj: A Walkthrough and Explanation

Description

Learn GitLab with Pj!

Links:
GitLab Markdown - https://docs.gitlab.com/ee/user/markdown.html
GitLab Doc - https://docs.gitlab.com/
GitLab Heroes - https://about.gitlab.com/community/heroes/
GitLab for Education - https://about.gitlab.com/solutions/education
Pj's Twitter - https://twitter.com/MetzinAround

0:24 - Pj intro
2:07 - readme in Learn GitLab
2:46 - what are issues?
3:22 - project Page Contents
3:50 - add new branch
5:25 - private vs public projects
6:00 - more project features and Web IDE
7:00 - heading to issues list v boards
7:39 - Issue 1: “Sign up for GitLab”
8:13 - Issue 2: “Create or Import your code into your Project (Repository)”
9:45 - “All of this is written in markdown”
10:44 - quick edits in files or Web IDE from file
11:08 - markdown docs
11:45 - import from GitHub
12:19 - back to the issues / sidebar navigation / pull request vs merge request
12:54 - Issue 2 closed
13:10 - Issue 3: “Create/import issues (tickers) to collaborate on ideas and plan work”
14:40 - comments in an issue and quick actions
16:11 - making a new issue
17:42 - Issue 4: setup CI/CD
19:38 - article for ci/cd Heroku link
20:40 - pipeline for Divas
22:30 - back to Learn GitLab
23:31 - set up CI/CD in a project
25:04 - looking into a pipeline
25:40 - GitLab Runners
26:23 - bring your own runner
27:58 - Issue 5: Merge Requests
28:52 - Gitpod
32:44 - creating a Merge Request
34:47 - Part 2
34:54 - Issue 6: Create a Milestone
38:23 - assigning issues
40:31 - issue edit history
40:50 - Issue 7: Invite a Colleague
42:14 - access Level
44:31 - Issue 8: What’s in free and what’s in the paid tiers of GitLab
45:25 - prices of tiers
46:15 - free licenses for qualifying Educational institutions
48:05 - Issue 9: Help and Resources
48:29 - GitLab Hero Program
49:21 - GitLab Docs
50:57 - Issue 10: Setup your Profile
52:57 - Issue 11: Using Container Registries & Docker images
54:00 - example of images in CI/CD
56:32 - showing Heroku for my bots
58:14 - thanks for watching!

A

Hi, my name is pj metz education, evangelist at gitlab, and this video is made of a couple of videos that I made kind of early on in my career at gitlab, uh where I walk through. What's called the learn, get lab project when you start a new account at gitlab, this project is automatically assigned to you and it contains several what are called issues that have tasks within them that help you learn how to use gitlab.

A

uh I was kind of new to gitlab at the time and I knew a little bit so I figured this was one a good way for me to familiarize myself with the product at the company I worked for, and it was a good way to show other people what they were getting as well, and I had to do it in two sections. I couldn't do it all at once. I was live streaming on twitch and when you live stream on twitch, you have a audience.

A

You sometimes get distracted and these streams that I did were originally about um 45 minutes to an hour long. Each and this video is going to be edited versions of those things. I'm doing my best to cut out the extraneous stuff where I'm talking about mountain dew or I'm talking about someone asked what shirt I was wearing. I was wearing an america online tank top and they wanted to know where I got it. So the normal stuff that happens in a twitch talk show style uh video. I I'm trying to get rid of that stuff.

A

So what you're going to see is you might see some jumps and edits? There's background music. The background music might not sing up sync up, but the reason I'm doing this because I want to have kind of just what you need in order to learn gitlab uh there will be uh down underneath here in the description you'll see some times that you can click on and take you directly to a section of the video, and I hope that this is helpful for you and I hope that you enjoy uh learn.

A

Git lab with pj learn gitlab and inside of it you'll see this readme, I'm going to zoom in a little bit.

A

So uh there's a bunch of tutorials it's contained in an issue and there's certain tasks. You have to complete um and view them. By going to up here we have issues and you can view them as a list or as kanban boards, and you complete each tutorial by working through the open list. When you complete it, you can drag the issue card to the closed list and then you move on to the next one. You can also do this in just regular um lists and you can just mark them as close.

A

So issues is the main way that git lab really kind of creates a a community of a lot of community involvement, but, like uh a word, called collaboration, why can't, I think of the word collaboration? It's the way. It creates collaboration. You open an issue to talk about what's going on in the code and what you want to change and what you want to do differently, etc, etc.

A

um So, if you don't need it, you can delete it here in the settings, but um I just want to take a second and sort of just go through what we're looking at here. So, first off, when you're in a project like we are flaps that uh up top you've got the icon, the name of it. A project id it'll. Tell you how many commits how many branches there are, how many tags uh and how much storage and you're using and how much is in the files um up here is where you can switch branches.

A

uh You can see that this is old. We uh made the the main branch. uh The default branch is now main. um I can actually change that really quickly very easily. So, let's add a new branch.

A

I'm going to call this one main based on master.

A

I'm gonna go here to branches, go to the project settings and in project settings I can change what the default branded branches.

A

I believe in you come on there we go okay and I can just change the default to main uh from now on, starting with gitlab, 14 um or possibly 14.1, which just released on the 22nd five days ago. uh The default branch will be main automatically on newly created uh stuff. So let's go back here to the repo.

A

And oh, no, we got to go back to branches, and now that main is the default you can see. It's marked as default master is protected, but I am the uh maintainer of this project, so I can delete the protected branch there. We go you'll notice that main uh on this particular project is not protected and that's okay, and um because it's just me in here, no one else has access like here. If you go to members.

A

Just me: that's an around right, I'm the owner, I'm not even a maintainer, I'm the owner, uh so no one else is gonna get in here. uh Let me make sure it's private, real, quick. It should be.

A

Yeah, it's private, so no one can even find it. If you have a public one, you can, of course uh it's very smart to protect your branches and keep anything from happening to them. It also keeps people who have lower access levels from being able to make unapproved changes. So that's really useful as well, so go back to main page here so now we're on main. This is where you can add a file or upload a file. If you got it on your local machine, you can create a new branch.

A

You can create a new tag. um This is the web ide. So if I wanted to work with some files in here in an ide, I can click this and it opens it up as like. A small ide right in my browser gives me the files right here, a ui for committing to the git, which is fantastic, uh new file, upload file, new folder, all that stuff. Let's look into readme here, okay, I can see it's written in markdown little preview time right here.

A

Everything you need is right in the browser. It's fantastic. uh Let's go back.

A

One of the things we don't have here is the ci cd, but because this is learning gitlab, I would bet we're going to add one later, so they told us in the readme to go to issues in the left sidebar.

A

So here's issues- and here it is as a list gives me all of the things I have to do in order to finish, and then we've got boards which will show me this is what's open.

A

This is what you need to do and then close and you can click and drag things into the closed one which is fantastic. It's I mean it's just really well organized personally. I prefer the list um sometimes I'm visually oriented, but I usually like a list better than the visual kanban boards, but I have used kanban boards before too all right so right here, it's sign up for git lab and, to be honest, I already did that because, like look there's my profile, so this one is is done. I I already did it.

A

I did what I was supposed to do. I gave it a thumbs up and I'm going to click close issue. This issue is now closed, which means it still exists, but we don't have to worry about it anymore. It moves to a different area, all right. Let's go back to our list number two create or import your code into your project into the repo you've already created your group and project within gitlab review the hierarchy once you're within your project. You can easily create or import repositories.

A

So with gitlab groups, you can assemble related projects together, grant members access to several projects at once, so, for instance, at work. I am a part of the community relations group and the education subgroup and that the community relations group gives me access to everything in there and, of course, the education one, that's more specific to mine and my managers uh goals and projects.

A

You can also have subgroups like it says, projects one or multiple projects for hosting a code base, use it as an issue, tracker uh collaborate on code and build tests and deploy with built-in gitlab ci cd, which we'll probably talk more about later. All right. You can also import an existing repository by providing the get url.

A

So, for instance, let's say you're on github and you you're making a move to get lab. It's pretty easy to uh do so so check it out. We're gonna do projects in the top navigation bar, then click your projects select the project you created then select repository once on the repository page. You can select the plus icon to add import files and you can review full documentation on creating repositories in gitlab.

A

All of this stuff is made in markdown. um I click edit. You can see. This is all written in markdown in the issue and it automatically uh creates this beautiful nicely organized pretty stuff. Okay. So to show you what they're talking about click projects and then click your projects, this is all different. Now this is getlab14 instead of having projects up here, it's all under menu.

A

So in projects. Let's look at your new favorite poem, which is the website. I build with brandon minik.

A

So what I did is I uh I added this uh from uh github. I was able to import it and it's got everything I need. It's got my readme, which is down here all nice and organized.

A

It's got, um get ignore. It's got all my files. So if you look in here, you can see my pages look at yeah index and let's say I needed to fix something real, quick like um just like. I made a small like spelling mistake. I can just edit this file the cshtml file here or I can open it into web ide and yeah adrian uh gitlab does have its own flavor markdown.

A

I don't know what the specific differences are, but I think it's based on cram down, if I remember correctly and here's the docs for that.

A

uh So that was just an example of showing what I need. So let's do. If I need a pretend, I need a whole new project go to my profile. Let's go to my.

A

I have a great pj awesome group.

A

Let's say I wanted to create a new project, new project, blank there's templates. I can import a project and I can get it right from github and as long as you authenticate with github and connect it to your github account, that's it so I've already done this before, uh because I did my importing earlier. So let's say I wanted to bring.

A

The hello world literally the first thing I ever did we like import that please and let's head to the issues and again you can uh collapse this and the only reason it's like that is because I'm zoomed in if you're at normal, it's always open. So you can see everything that's over here. You can look at merge requests which are called pull requests in github um ci cd here and when you hover it gives you um some options as well, but I don't have any ci cd right now because I haven't set it up.

A

So let's go back to the repo and let's zoom in again.

A

So uh I already did this: I completed all my tasks. It even shows you. If you have tasks inside of it, it creates this right. There marked it all imported files and it's closed. We are moving right along. Aren't. We folks all right create slash import issues to collaborate on ideas and plan work, but, as you can see, I already did this one before so. Issues allow you and your team to discuss proposals before and during implementation.

A

They can be used for a variety of other purposes, customized to your needs and workflow uh they're always associated with a specific project. So when you make an issue it needs to be within that specific project. um There is also something called epics, but that's a like ultimate get lab thing. uh So, unless you're at a company, that's paying for the ultimate licenses, you're, probably not gonna, be working with epics, mostly.

A

So, um if you have multiple projects in a group, you can view issues at the group level as well, and you can review this issue, documentation everywhere, well, not everywhere, but specifically at this link, but we're good uh existing issues or tickets. You can import them as long as they are uh formatted as a csv file and there's an import process, for that so reasons to have this is to discuss the implementation of a new idea to track tasks. I know that my boss and I use it when we've got an idea.

A

For instance dj you should probably host a twitch show where you introduce git lab to people and talk about how to use it. I was like okay, but what would that format look like, and all this takes place inside of an issue in comments, so you can have designs here. You can do that. You can have you can see all recent activity then down here. You can make comments um so, as you can see, markdown and quick actions are supported. We have some specific, quick actions related to gitlab that are pretty cool.

A

We do have there's one, that's like a shrug.

A

Where is it yeah just shrug comment?

A

Actually, let me try that right now.

A

I love you internet, I love you so much all right. um So yeah you can do your comments and you do it back and forth and then eventually, once you've either completed the task. The issue is for or it's no longer relevant or, um for instance, you can have milestones attached to them. Once the milestones passed you can close. It.

A

Let's close that.

A

All right, so you go to projects, you pick a project. uh You can select issues. You can make new issues very easily uh if you're looking at the full list, there's just a blue new issue button boop all of this stuff, let's go over making a new issue. Actually it's pretty straightforward! So hey big blue button, here's a title! You can have um what are called templates and that would show up here, but because this project doesn't have any templates right now, uh none are showing up.

A

So normally, this drop down says uh issue like bug report, for instance, and so you can see add description templates to help your contributors communicate effectively, and this takes you to what you can do and you can read more all right, so you would make your title: what's your description, you can assign it to somebody.

A

uh I usually assign it to myself um to make sure that it shows up for me because, when it's assigned to you, it shows up here under the issues link and it shows up as a little like you have a issue here. uh This is merge request there. If you have a merge request that you're responsible for that pops up there and then to-do list, uh we'll talk more about to-do lists later on, uh you can make it confidential. You can add a milestone right here.

A

You can add labels and you can make a due date and then you would just create it and it would show up.

A

So we just finished that we know all about issues now, so we can close it nailed it. We get guys we're doing great we're doing really. Well, I'm very proud of us. So that's closed. Let's head back to the issues, all right set up, ci cd- and you can see like I've already done this before, but we're gonna pretend I haven't y'all all right.

A

Cicd stands for continuous iteration, continuous development or continuous deployment, and it is a process by which you are changing code and iterating and making changes to a code base and simultaneously having the ability to deploy it somewhere or to push it back to production and gitlab has a very heavily automated set of how ci cd works. So so, integration, like I said, works by pushing small changes to the code base in a git repository and for every push.

A

It runs a pipeline full of scripts that builds tests and validates that code before it ends up merged into your main branch. So this is a way of making sure that the code, you're writing, doesn't break stuff like a blimp, biscuit song, delivery and deployment is deploying the application production at every push to the default branch. Specifically, delivery is uh like setting it up for that, and then you manually push it and deployment automatically. Does it so to show you to go to divas?

A

I have uh the ci cd setup on divas and if we go to the editor, so your ci cd is written in yaml, which is a uh is not yet another markup language, and the first thing we do is we declare an image to use and I'm going to show you in the pipeline. What all this looks like too uh a couple scripts run to make sure that we've got everything updated and installed and everything's ready to do what it needs to do.

A

I got all of this from a article that taught me how to do ci cd to push to heroku, where my divas are hosted.

A

uh You declare stages at the beginning, and then you say what stage each job like this is a job here, job called production, it's deploying it's the stage of production, it's using a ruby image and then this script here pushes it to heroku, and this is directly from heroku about how to do it. When this runs, it only does it on the main branch when this runs.

A

So it reads, it reads: an update to main the pipeline runs when it gets down to this job. It automatically pushes those changes to heroku and then on heroku's end. It flips it around and uh pushes the code into there and it runs it over there and then you can tweet it shania mod again. As far as I'm concerned, it's black magic. I really the ins and outs not for me. So let me show you what those pipelines look like when they're running and you'll see a bunch that have failed, probably in the past.

A

Oh, it's been doing pretty well, so it shows you all the pipelines that you've run in the past, so I've done some updates to the nsync javascript to shania change the date on some of them and when you're looking at these pipelines.

A

If you click here on the status, it pulls you into a visual and it shows you the job. Remember that job was called production, so we've got production here and here's the full log for it.

A

And it shows you everything that was happening. If there's an error, it'll tell you what's going on, you can see. This is the script that pushes it to heroku and these keys are inside of uh heroku. So these are uh variables that live at heroku.

A

It knows what the app is, and it knows what the api key is.

A

There's the deploy, see it's pushing uh it's, it says it's a node app detected, it creates a runtime environment. It puts all this stuff in installs the binaries builds, it builds, succeeded, you're, good and then it cleans it up and it says: hey job done.

A

Like I said, it's pretty dope.

A

Thank you. Thank you. That's enough of that.

A

um So that's how that pipeline looks so, let's head back to the learn, get lab project and let's see what they want us to do, for ci cd.

A

You can watch a demo, you can read the docs, so it says read the following: documentation: how gitlab ci cd works, pipeline, architectures, basic workflow and a step-by-step guide.

A

When you're ready, select, ci cd and start setting up the ci cd in your project, so because this like uh this project and the issues, are telling you to go and set up cic in another project. So it's kind of this cool parallel thing where this project helps you learn while you're setting up another project so to make.

A

Let's say what did I just import?

A

Oh, that fake hello world, so there's a bunch of options up at the top, um adding a license: change, law, contributing, etc, etc. Thank you aj. How are you not following me already, so all I did there was um from the main project page leave, there's a button for setup, ciacd, just a quick action here and if you create a new pipeline, it just automatically makes the file that you need for it, which is called dot, get lab, dash, ci, dot, yml.

A

You can see it's a template and obviously you you, if you're throwing a template down, you got to make sure to check and see if it needs to change anything before it runs for your project.

A

You can see that it's got some information about what this is so first, you declare your stages, build test, deploy you create a job that you can name almost anything they're like this is called build job. It stages, build the script and it just has two echoes just says those things um unit test, job echo, running tests, sleeps for 60 seconds and then another echo, uh a lint.

A

You can run lint in your ci cd and then you can deploy it, and this is something it'll run, because it's just a bunch of echoes which is fun um so yeah, I'm gonna, I'm gonna, keep this, I'm gonna say created gitlab ciml file and commit that, and then it's going to run that pipeline.

A

So it says: hey this pipeline's running, you can click into it.

A

And it shows you your jobs, each individual job under an individual stage right, so you can see, build job is completed when we click into it.

A

Let's find that echo yeah echo compiling the code compile complete. Obviously it's not really doing anything. It's just an echo but um you'll see up here at the top. It says running with git lab runner, 14.1.0, rcl and then a bunch of numbers. The gitlab runner is something I did want to talk about. Rci cd only works with what are called git lab runners, which are written in go, and they essentially take your yaml and make it work. uh You have to have a runner.

A

um This is using, what's called a shared runner, that just means it just it exists and kind of everyone on gitlab.com has access to it. So if they're really busy, I mean there's tons of them, but if they're busy your job takes a little longer.

A

So let's say you've got a big company and you want to use git lab but you're like well. We don't want to use the shared runners necessarily also. We want to make sure that our runners are perfectly optimized for our work. Well make your own runner and I was actually doing this uh last night. I was practicing ci cd and I was making runners on my uh machine and you can actually let me pull up my terminal that, oh it's like that's such a small terminal.

A

uh Let me see, get live runner.

A

There's just a status yeah.

A

And I started uh a few gitlab runners on here and if I do a list, it'll show you so I have one with a default description and one with the tags and one for ci cd certification. I was basically making these as part of practicing learning git lab last night. um That process for making your own uh runners is well documented, but you have to have a runner and a dot get lab dash, ci dot yml file.

A

In order to do ci cd, you can see it uses a lot of docker um images runs everything inside of that and then just it does its thing. So that's cicd. Let's go back to learn gitlab. We can mark that issue as close set up ci cd moving that over here that's closed now and if you click into it, you'll see it's no longer there. So if you move it on the kanban board, it automatically closes it for you, which is great uh first merge request, like I said earlier, get lab.

A

We call a merge requests, you might know them as pull requests. uh We see it as you're asking for something to be merged into the main code.

A

So this lets you uh visualize and collaborate on proposed changes to source code that exists as commits on a given git branch. Yeah lets you see what you're trying to do.

A

So if you go to projects you can create a merge request. So I'm going to let's do this in divas and I'll just do it with the readme, because that's I'm not trying to change anything crazy today.

A

So, let's head into web ide and one of the cool things we have by the way um is I've integrated with gitpod, which is something available to uh people with gitlab.com gitpod creates visual studio code directly in the browser, and this is fully integrated with gitlab.

A

And now I can work with vs code directly in my browser and I never have to pull anything locally, and so I don't have to worry about pushing and pulling and fetching and all that it's just right in vs code right here you see it gives me a unique url up here.

A

And here's all of my diva stuff right there, let's zoom in a little bit- and I said I wanted to mess with the readme.

A

Tag chloe here: that's what I'll do I'll tag our twitters do that, let's.

A

A

Then, let's add my twitter.

A

A

I always do that. That's in a rounded okay, so I have done that here uh in git pod, which is again just vs code instance right. My browser, I'm still on edge and let's head to the get and we'll see that there are changes to readme.

A

Stage changes so this to commit on main, but I don't want to commit on maine. I want to commit to a new branch.

A

Let's see commit committee page now so check out two: let's create a new branch called changed readme. Let's, actually, let's do.

A

Ejm me change there. We go all right so now here I am I'm on the new branch, because I did all this in uh get pod, which is ps code. um I'm on the new branch. I've got the stage changes here, I'm going to commit my message: changed readme to add twitter account for chloe and pj.

A

Oh four characters over. Oh that's right! The message has to be short uh added twitter links. There we go, um I can go ahead and commit that so that's committed now and I can push it and so you'll notice. I created this. The branch here in get pod technically, there's no upstream for it. It's like hey that doesn't exist in the repository.

A

Do you want to? Would you like to publish it, and so it gives you that option to go ahead and do that just like in vs code? It's like I mean it is it's via it's vs code y'all like this is.

A

All right, all of that's there, we are in this weekend to do head back, diva's life.

A

I'm gonna refresh this just to be sure.

A

Bjm readme change.

A

And here's the branch.

A

And you'll see right here, so I've updated that I've got a branch and.

A

We need a merge request, so we've got the branch we need to ask to merge. It.

A

So we've got the source branch. This is going to be djm. Readme target branch is main.

A

Title this is a big one um inside the description you should always put why you're doing it.

A

Always saying why is just it's a really good idea, because that way, the person who's doing the merge requests for you, who's actually merging them together knows why you made it. Don't just tell me what you did tell me: why you did it, because we need some reasoning. We can't just merge everything in telling us why help slips move that along a lot faster.

A

Okay, I saw you can assign it to whoever is responsible for merging it. You can delete the source branch once you're doing it. You create the merge request.

A

This is what the merge request looks like. It tells you what's going into what it says: approval is optional. You can ask for people to approve and then finally, if you're able to merge, you can do this and you're going to see that I'm able to because I'm the only person on this project, I click, merge and it's merged, and then the source branch gets deleted. There's no pipeline because I deleted it.

A

Let's look at making milestones, so milestones are a way to track issues, uh merge, requests, etc, etc, and it's a way to keep track of. What's due, what's what's coming up stuff like that, uh I set up my milestones for work last week and my boss, and I we work in two-week milestones with the final milestone being a three-week milestone and we're both pretty good at uh sort of spreading out the work uh and making it so that um it's not a a sprint at the end to just cram a bunch of stuff in there.

A

So let's talk about how we're gonna do this, as always documentation, link right here, but we're going to go to projects your project select the project. You've created click on issues then milestones. So if we were in learn, git lab that'd be right, there click new milestone and then name it start net and create milestones. So, let's head to say, divas.

A

So we're gonna go issues milestones.

A

New milestone, we're going to call this one forever, we'll have it start today, we'll have it end on september 3rd, which is the first day of halloween horror nights in orlando.

A

Countdown milestone to hhn orlando, those of you that don't know halloween horror nights is my favorite time of year.

A

You can write in markdown if you want.

A

I wanted to italicize hhn.

A

Do that create milestone? Take me right to it.

A

Then this is the milestone, but there's nothing in it. uh You would have to go to the issue.

A

So if you want to add it, there's a first off there are, as you can see, uh two sidebars when you're looking at kit lab it's one down here, that's uh the one that you end up using a lot and when you're in an issue or something that has some properties and characteristics, it's got your assignees, your milestones due dates, etc. So, if we want to add a milestone, this is forever that we just created now that milestone is connected to this issue.

A

So if I wanted to go to milestones, I can go to menu milestones.

A

And it'll take a second.

A

Here's the milestone.

A

And there we can see it now, there's an issue in here scroll down, it's unstarted, it's open, it's unassigned! All I have to do is assign that to somebody.

A

Signing it to myself we'll go back to milestones.

A

And now it's moved from unstarted, open and unassigned to open and assigned uh assigning issues is a great way to uh keep track of who's. Doing what um you have multiple people assigned uh to an issue, and then it uh lets people see what they're responsible for uh you'll notice now that I've assigned that to myself up here on the top right is issues and I'm gonna zoom in just a little bit to make this a little easier for you guys.

A

So up here is issues when you're looking at the list down here, picked up yep. That's where I put all my pictures that I needed for my readme. That's the issue I just assigned to myself. It now shows up here that you can use as a sort of reminder of what it is you need to be doing.

A

So those are the issues there. Any merge requests would be right here and then this is actually to do if you're tagged or assigned sticks it in your to-do. You can be like ah thanks to-do list, I'm done with that. It doesn't remove you as an assignee if you've been assigned it just gets rid of that notification.

A

I'm still assigned to the issue that I just had see the only way to get rid of myself literally unassigned.

A

Let's go back, projects learn gitlab.

A

Hey I'll head to issues your list.

A

A

I forgot uh they can have a hard time when you click a to-do item. It takes a second to reload uh to because it's a change inside of the edit, so it's like remaking it every time. uh So now we can assign issues which we did while viewing an issue.

A

Good thing about this is um when you're in an issue. It can actually show you what's happening inside that issue over time. You get a little history timeline down here. All right go back to that list.

A

We need to mark this as deleted. All right next is invite a colleague, I'm gonna, invite all of you. Everyone who watches this.

A

So one of the things I always talk about is um being an individual developer versus being a part of a team and if you're part of a team I feel like gitlab is great for collaborating uh everybody at gitlab uses gitlab, uh it's literally. We have slack but you're having a conversation with slack about something, almost always someone's like hey. Let's move this to gitlab and what we do is we create an issue for it?

A

So it's so it's got so many great tools, but a lot of those tools are for collaboration. So if, like you're, an individual developer and you're doing something all by yourself, it might be that git lab isn't right for you.

A

If you're doing ci cd, though I mean, I think there would be reason to consider it at least, but our big thing that we're really good at is collaboration is creating an environment where everybody can participate where everyone can contribute and where people can excel as a team, because you don't have to leave, get lab to have all these great tools for teamwork, you don't have to go and get another app and connect it to your repository.

A

It's all inside gitlab, all in one, the devops solution.

A

So when you've got a team, obviously you don't want everyone to be the owner of the repo and be able to delete and commit to maine and to be able to force push and all that stuff. You want to uh limit the access of certain members, you know, let's say you're running an open source project and you've got people who want to contribute.

A

You don't want them to have access to absolutely everything that can be a security risk, so you can assign them access levels. You can make them developer. Maintainer owner, you probably want to want to make someone owner, but making them a maintainer if they're well trusted- um and we got documentation on this. So when you're in projects you go to your project, settings and members and you invite them by entering their email and that's going to be right up here. Project information remember this is the sidebar over here project information members.

A

I think there's technically a.

A

A bot- that's a member here, but you can see who's already, a member you can see where they came from if they're a direct member of the group or if they were added in because they're part of another group that has access when they got it when their access expires and what their maximum role is within the project.

A

You can leave the group if you want, but uh not recommended, so when you're inviting people it can be by email address or gitlab member, you can give them a role: guest reporter developer, maintainer.

A

When their access expires, you can invite them or you can import and there's. Also you can invite a whole group from get lab.

A

I don't. I only have two groups in my gitlab instance. Obviously, there's a lot more if you're, using the uh assass version of gitlab.

A

So that's! Oh! No! There we go! That's that I'm gonna mark this as done I'm not inviting anyone to my personal group. Thank you very much.

A

And then we close the issue. That's closed head to the list.

A

Now this is where we start to actually learn what git lab gets you, so the free version of git lab totally free. No time limit. There are some restrictions, uh ci cd minutes. For instance, you only get a certain amount of ci cd minutes with the free tier, um but uh obviously when you're getting into like paid gitlab you're gonna get a lot more features. I mean that's how description services work.

A

Really I didn't have to tell you that um if you want to upgrade it, you do it on the billing page and you can find the billing page in the account by clicking on the avatar. So while I have you here, I mean look like this: isn't just a stream of me playing video games. This is me showing y'all what my my job has so again. Free uh you gotta. You bring your own ci runners in order to use the ci cd uh 400 ci cd minutes per month.

A

uh If it's a self-managed, then your self-managed runners are for you and that's that's that um premium 19 per user per month, but you bill it annually um and then you get all of this plus uh some better, better stuff. Just like it's, it's the best that you can get um advanced security testing for like uh das and I think sas as well um container scanning fuzz testing stuff. I don't know.

A

uh Portfolio management, you get 50 000 ci cd minutes per month, so if you're doing a lot of ci cd, then you need that.

A

So that's the uh stuff you can get for that now. One of the cool things that I do is I'm on the education team now git lab for education.

A

We offer uh free licenses for educational institutions to use for education or research, so, if you're using it in a classroom free if you're using it for research free all of that totally free, you just have to apply.

A

um If you want to use it for, like your campus, like everyone on campus, then that's a totally different um subscription for a classroom, say you're teaching, computer science, and you want to do some devops stuff, because you want your students to be prepared for the work environment they'll be joining, then you can get those licenses for total frizzle.

A

That's free! um We've also got uh some student, spotlights we've got uh hackathons, we're always looking for contributors, everybody can contribute. um We've got some case, studies of schools that have used it really well, and that's constantly evolving and changing and we're always bringing more and more and more um schools on. We just recently hit over a million active users using the free seats that we provide and, like we said you can use it in um research as well.

A

So as long as your research isn't for turning a profit uh you're allowed to use it so tell people, you know what we got all right: let's go back issues.

A

Go ahead and mark that as completed help and resources, the lab is open source community. First, um we are an open core company. uh Literally you can come in, you can get it free. You can start contributing to gitlab immediately to our docs to the project itself.

A

um And if you stick around enough, you can become a gitlab hero and if you beyond that, we even have like a um a core team which is pretty cool, so get live. Hero program, we're looking at people in the community that are really doing a lot with git lab and participating in our open source stuff, and we make you a gitlab hero and you can uh apply here.

A

You know this is just the way that we try and keep our community engaged. You can see, we've got contributors, heroes and superheroes, and a contributor you've got five merged. Mrs or one really good one uh to improve, get lab and that's again, that's the application itself, the website or the docs. We are always looking for people to contribute to uh what we're doing so support team is for paying customers but account related issues. uh You can always uh get on our support page.

A

So again, our docs are here at docs.gitlab.com.

A

And search for anything, so let's say you want to do cloud deployment.

A

We've got docs on how you can use getlab to deploy directly to the cloud using your ci cd. um You can even run uh aws commands directly from the ci cd, and that was in 12.6 we're on 14.1 coming on 14.2 on august 22nd, so our docs and I really think our docs are pretty pretty pretty good. um Honestly, like I don't know, I'm partial, but I think I think our docs do a pretty good job. Obviously we're always looking to improve.

A

So, if you're in our docs and something isn't working for you or it's hard to find something or you think the information is a little light. Tell us open up an issue in gitlab. Let us know- and we are absolutely more than happy to uh take any suggestions that we can to improve. We've got a forum. We got gitlab on stack overflow, any questions that are tagged as git lab. Everyone knows stack. Overflow is where you go to figure out, what's going wrong.

A

um So if you've got a specific question, you check here first see if someone else has asked it or if it's getting a lot of engagement and then you can always follow gitlab status or head to the status page profile and status, pretty straightforward. It's very you know, surface level, setting up your profile lets people know you one of the things that we have in the profile now.

A

A

I always capitalize it and I feel like I shouldn't, because then I feels like jesus. uh If your name is pronounced, uh non-english phonetically or if it's a specific pronunciation that you um you know always get your name mispronounced, you can write it out. Phonetically here your email, don't show your email on profile. My commit email, skype, linkedin, twitter website, all this stuff that you can have um and that way. When people looking at your profile, they can see you and the pronouns is actually available on hover.

A

um If you hover over somebody's profile, when they've like commented on something it'll show you their pronouns. So when you go to talk with them, it shows you exactly how they prefer to be uh addressed. You can see my activity is a little a little light.

A

I think my work, one is a little uh better yeah the work one's a little bit more active um and I keep my work one on dark mode, because that's the one I use more often I keep my personal one on light mode, because it helps me know immediately what I'm on, if gitlab's in light mode. I know I'm on my personal account. It's in dark mode, I know that's my work account and the pronouns came with get lab 14, which was july 22nd, but june 22nd actually was 14.

A

A

Didn't emoji made a status updated my personal settings. One of the reasons you might want to consider using git lab is for rci cd.

A

In addition to the uh nrci cd, you can use uh docker engines and that's where you're gonna test and build your application and to make that happen. It's a pretty uh straightforward process. You just kind of say use this image at the top. So those who don't know docker is an open source project that allows you to use predefined. What are called images to run. Applications in independent containers that are run with a single linux instance.

A

So docker hub has a bunch of pre-built images that can be used to test your applications and that's the advantage of why you would want to use gitlab in the first place is because we make testing easy so if using it with continuous integration, docker runs each job in a separate and isolated container, using the predefined image set up in your gitlab ci dot, yaml file.

A

So to show you what that looks like. Let me take you to my divas, my divas. uh When I update the main branch automatically deploys to heroku using instructions that I wrote in this file, so you can see the image I'm using the latest known image from docker when this runs uh I'll. Show you a log actually um after this.

A

uh This is all the stuff that runs before anything else.

A

You have to declare what stages there are in this, and really the only thing I use this for with my divas is for um uh deploying to heroku and for heroku. When I looked up uh the instructions on how to deploy to heroku, it suggested using ruby. So I did and then I've got these uh variables here that heroku knows, and it just sticks it right on my heroku instance, so I'll show you guys see, let's go to ci cd. So again, this collapsible sidebar over here cicd is the little rocket go to pipelines.

A

You can see previous pipelines that I've run.

A

So each pipeline, like I said, has a set of stages and each set of stages has a set of jobs. That runs and you can click and you can see the jobs here. So it's called production and the stage is production so, like I said it picks a runner, and in this case it's just a shared runner from git lab, tells you its number and everything, and it says we're running on docker.

A

Pulls the image prepares, the environment grabs the variables that it needs. That's the updates you can see in green. That's when it's a script that it's running another script.

A

Now the script down here are those uh variables right prepares to deploy cleans it all up, deploys the application.

A

Down at the bottom cleans up everything and then lets. You know that the job succeeded.

A

um On the other side of that is heroku, so um I used to run all of these uh applications as separate apps and each one had its own dyno and I ran out of free dino minutes very quickly. So that's why, when we're looking at um my divas, which are my twitter bots, that I have uh connecting these two connecting gitlab and heroku, I actually looked up an article to do.

A

There's as anyone who's been developing for a while knows, there's instructions for literally like almost everything out there, but uh we can view the logs here on heroku of what's happening, and here we can see it tells me that it tweeted at me.

A

uh We also have under activity you'll see the last time I deployed you can compare the disks. You can view the build logs here, real good content, real good thanks, jelly man. You embarrassed me in front of everyone: real good quality content.

A

Let's go back to this.

A

So, like I said, uh this is where all the ci happens and uh using docker is as simple as just playing an image at the top. So, like I said, the reason you'd be using docker is because it's a reproducible build environment. That gives you everything you need in order to test out your application. It makes sure that it works.

A

So when you deploy it, you don't have people going, it doesn't work, so there's tons of documentation on it. um How to use a container registry, how to specifically use docker images, how to install docker within git lab, hey. It's me again just wanted to wrap up this video and let you know if you wanted to learn anything else, be sure to check out our docs. uh If you have any questions, feel free to tag me on twitter at mets and around. I think I'll put it right here.

A

So if you wanna, let me know on there how you're doing with your uh learn modules. If you have any questions, I can help you find the answers, uh but I hope this has been useful for you. I hope this is beneficial and I hope to see y'all online see you around.

A