Waubonsee Community College

We have now covered the basic features of GitLab that should handle all your day-to-day software development needs. The time has come to look at some of GitLab’s specialized features that you might miss, at least I did when I first started using GitLab. In this chapter, we are going to focus on GitLab’s facilities for storing generated objects to be used by other developers. There are a number of them, but we’ll focus on two in particular: the Docker container registry and the binary package registry.

Now that we have covered managing source code and directories within a project as well as creating pipelines to build and store artifacts for deployment, the time has come to look at how to organize our projects in a multi-team environment. In this chapter, we will cover how to manage multiple projects under a group as well as creating subgroups within groups. As part of this discussion, we’ll look at how roles are used in conjunction with projects and groups to determine the permissions of team members assigned to those projects and groups.

I mentioned in Chapter 1 that in order to illustrate the various features of GitLab, which we’ve just now completed, it was easier to create an account on gitlab.com rather than install GitLab as a self-managed service. This is because installing GitLab on your own is much more involved than simply downloading a binary and installing it. There are a lot of moving pieces to a self-managed GitLab. The good news is, there is more than one way to install GitLab. The bad news is, there is more than one way to install GitLab.