GITLAB_HOSTNAME=gitlab.local
GITLAB_HOME=${HOME}/var/work/gitlab
OMNIBUS=""
OMNIBUS+="external_url \"http://${GITLAB_HOSTNAME}:8480/\";"
OMNIBUS+="gitlab_rails['gitlab_shell_ssh_port'] = 8422;"
function start() {
[[ -d ${GITLAB_HOME} ]] && mkdir -p ${GITLAB_HOME}
docker run \
--detach \
--hostname ${GITLAB_HOSTNAME} \
--env GITLAB_OMNIBUS_CONFIG="${OMNIBUS}" \
--publish 8443:443 \
--publish 8480:8480 \
--publish 8422:22 \
--name gitlab \
--restart always \
--volume ${GITLAB_HOME}/config:/etc/gitlab \
--volume ${GITLAB_HOME}/logs:/var/log/gitlab \
--volume ${GITLAB_HOME}/data:/var/opt/gitlab \
gitlab/gitlab-ce:latest
}
startIntroduction to Gitlab
What is GitLab
Target audience
Scope & Terminology
GitLab setup
GitLab setup prerequisites
Gitlab docker setup
Gitlab account setup
Figure 1. Admin password setup
Figure 2. User account creation
Figure 3. Define role
Module 1 - User configuration
Goals
User profile configuration
Navigate to the user' settings
Figure 4. Navigate to the user settings
Change the avatar
Figure 5. Change the avatar
Figure 6. Upload new avatar from image file
For Joe Developer the chosen avatar is a construction worker with hard hat.
Review privacy settings
Figure 7. Privacy settings
Figure 8. Upload a ssh public key
Figure 9. Upload confirmation for ssh public key
Module 2 - Gitlab project
Goals
Create a new project
Figure 10. Create a new project from the top navigation bar
Figure 11. Fill in the required information
Figure 12. Initial project overview screen.
Clone project
Navigate to the overview page of the project → http://gitlab.local:8480/jdev/gitlab-project
Figure 13. Copy project address for git clone operation.
Repository protection
Figure 14. Restrictive master branch settings.
Module 3 - Forking projects
Goals
Create new user (fork)
When finished change the avatar to match the description.
Figure 15. Mary DevOps user profile page
Create forked project
Figure 16. Fork the project
gitlab-project
Figure 17. Select namespace for the fork.
Figure 18. Fork in progress screen
Figure 19. Forked project overview page.
Change content of forked project
Push changes to project
Navigating once more to the project page of the fork → http://gitlab.local:8480/mdevops/gitlab-project/ to view the changes in the interface.
Figure 20. The forked project’s page after the push
Switching the project’s view to branch documentation.
Figure 21. The branch
documentation in the overview.Summary
Module 4 - Merge requests
Goals
Create merge request
Initiate merge request
Figure 22. After pushing a branch notification appears on the overview page.
Alternatively open a merge request via left hand side menu
Repository → Commits
Figure 23. Create merge request via
CommitsA third way is to go via the left hand menu Repository → Branches
page.
Figure 24. Create merge request via
Branches
Figure 25. Create merge request via
BranchesReview merge requests
View merge request
Figure 26. Merge request right after submission.
Add comment
Figure 27. User Joe Developer adds a comment under changes.
Figure 28. Mary DevOps views comment and resolves thread.
Amend request
Figure 29. Create a suggestion
Figure 30. Submit the suggestion as review
Figure 31. Suggestion ready for review or application.
Figure 32. Applied suggestion.
Merge the request
Figure 33. Merge the request
Post merge review
Web UI post merge review
Figure 34. Project overview page post merge.
Figure 35. Review of the commits present.
Module 5 - Submodules
Goals
Add a submodule to repository
Create a new project submodule under the GitLab frontend.
It will be used as the submodule repository for the following
excercises.
Push with submodules
Figure 36. Repository
submodule after merge
Figure 37. Repository
gitlab-project after merge