GitLab - Revision history

Leo at 17:22, 7 December 2022

2022-12-07T17:22:26Z

← Older revision		Revision as of 17:22, 7 December 2022
Line 45:		Line 45:

	== Upgrading ==		== Upgrading ==
	When upgrading, review the change logs to determine the appropriate upgrade path. ~~In general, your~~ upgrade ~~path needs to go through all the major revisions. For example, starting from 13.8.1 and upgrading to 14.3.0,~~ you ~~need to hop through to 13~~.~~8.Z, 13.9.Z, ... 13.12.Z, 14.0.Z, 14.1.Z, ..., 14.3.Z~~.		When upgrading, review the change logs to determine the appropriate upgrade path. The upgrade paths that you should take can be determined using this tool: https://gitlab-com.gitlab.io/support/toolbox/upgrade-path/

	~~As a result~~, ~~upgrades~~ should be scheduled periodically to avoid falling too far back.		In general, your upgrade path needs to go through all the major revisions. For example, starting from 13.8.1 and upgrading to 14.3.0, you need to hop through to 13.8.Z, 13.9.Z, ... 13.12.Z, 14.0.Z, 14.1.Z, ..., 14.3.Z, where Z is the highest release number in that version. Use the upgrade path tool above to determine which versions are not required.

			Upgrades should be scheduled periodically to avoid falling too far back as it may complicate the upgrade process and expose you to security vulnerabilities.

	==CI/CD Setup==		==CI/CD Setup==

Leo at 18:08, 12 November 2021

2021-11-12T18:08:10Z

← Older revision		Revision as of 18:08, 12 November 2021
Line 1:		Line 1:
	<br />		<br />

	== Installation ==		==Installation==

	=== Docker based ===		===Docker based===
	Using docker-compose, we can quickly deploy GitLab with the following service definition. GitLab will be served on port 8888 with the registry served on port 5001. I then use Traefik (configured using container labels) to expose GitLab to the internet.		Using docker-compose, we can quickly deploy GitLab with the following service definition. GitLab will be served on port 8888 with the registry served on port 5001. I then use Traefik (configured using container labels) to expose GitLab to the internet.
	{{Highlight		{{Highlight
Line 44:		Line 44:
	The unicorn/workhorse pod used to drive the GitLab web application gets its configs from the {{code\|gitlab-unicorn}} ConfigMap.		The unicorn/workhorse pod used to drive the GitLab web application gets its configs from the {{code\|gitlab-unicorn}} ConfigMap.

	== CI/CD Setup ==		== Upgrading ==
			When upgrading, review the change logs to determine the appropriate upgrade path. In general, your upgrade path needs to go through all the major revisions. For example, starting from 13.8.1 and upgrading to 14.3.0, you need to hop through to 13.8.Z, 13.9.Z, ... 13.12.Z, 14.0.Z, 14.1.Z, ..., 14.3.Z.

			As a result, upgrades should be scheduled periodically to avoid falling too far back.

			==CI/CD Setup==
	GitLab has a built-in CI/CD pipeline feature that can automate certain tasks when code is committed into a repository. Some examples of CI/CD pipelines include compiling/building releases, running unit tests, or triggering certain web hooks when code is committed.		GitLab has a built-in CI/CD pipeline feature that can automate certain tasks when code is committed into a repository. Some examples of CI/CD pipelines include compiling/building releases, running unit tests, or triggering certain web hooks when code is committed.

	CI/CD pipelines can run in various ways. Most common is to use a Docker container to run CI/CD code in.		CI/CD pipelines can run in various ways. Most common is to use a Docker container to run CI/CD code in.

	==== Docker based ====		====Docker based====
	I run the GitLab runner on a separate docker host from the GitLab instance. This is because GitLab runners will run with privileged mode and at worst pollutes the production docker environment with heaps of temporary build containers, and at worst can potentially interfere with the production GitLab environment.		I run the GitLab runner on a separate docker host from the GitLab instance. This is because GitLab runners will run with privileged mode and at worst pollutes the production docker environment with heaps of temporary build containers, and at worst can potentially interfere with the production GitLab environment.

Line 119:		Line 124:
	==Troubleshooting==		==Troubleshooting==

	=== Failed to create listener - address family not supported ===		===Failed to create listener - address family not supported===
	Runner container crashes with a fatal error message:		Runner container crashes with a fatal error message:
	{{highlight\|lang=text\|code=		{{highlight\|lang=text\|code=
Line 132:		Line 137:
	}}		}}

	=== Docker-based CI/CD runner fails - docker no such host ===		===Docker-based CI/CD runner fails - docker no such host===
	My CI/CD pipeline fails with the following error:		My CI/CD pipeline fails with the following error:
	{{Highlight		{{Highlight
Line 146:		Line 151:
	Remove/restart the runner and restart the pipeline.		Remove/restart the runner and restart the pipeline.

	== Tasks ==		==Tasks==

	===Registry Cleanup===		===Registry Cleanup===

Leo at 05:13, 8 November 2021

2021-11-08T05:13:11Z

Show changes

Leo: Updated categories

2020-06-15T00:16:47Z

Updated categories

← Older revision		Revision as of 00:16, 15 June 2020
Line 179:		Line 179:
	}}		}}

	~~{{Navbox Linux}}~~[[Category:~~Linux]]~~		[[Category:Containers]]
	~~[[Category:LinuxUtilities]]~~		{{Navbox Web}}[[Category:WebApp]]
	~~[[Category:Docker~~]]
	[[Category:~~Todo~~]]

Leo at 22:01, 14 June 2020

2020-06-14T22:01:56Z

← Older revision		Revision as of 22:01, 14 June 2020
Line 180:		Line 180:

	{{Navbox Linux}}[[Category:Linux]]		{{Navbox Linux}}[[Category:Linux]]
			[[Category:LinuxUtilities]]
	[[Category:Docker]]		[[Category:Docker]]
	[[Category:Todo]]		[[Category:Todo]]

Leo: /* Backups */

2019-10-25T15:39:00Z

Backups

← Older revision		Revision as of 15:39, 25 October 2019
Line 159:		Line 159:

	== Backups ==		== Backups ==
	GitLab using the Helm Chart can be backed up by running {{code\|backup-utility}} inside the GitLab runner container. Backups that are generated will be placed at {{code\|/srv/gitlab/tmp/backup}} as defined by the {{code\|backup.path}} parameter in {{code\|/srv/gitlab/config/gitlab.yml}}.		GitLab using the Helm Chart can be backed up by running {{code\|backup-utility}} inside the GitLab runner container. Backups that are generated will be placed at {{code\|/srv/gitlab/tmp/backup}} as defined by the {{code\|backup.path}} parameter in {{code\|/srv/gitlab/config/gitlab.yml}}.

	Omnibus GitLab can be backed up by scheduling a task that runs {{code\|/opt/gitlab/bin/gitlab-rake gitlab:backup:create}}. ~~Certain~~ components can be skipped by passing in the {{code\|SKIP}} value. For example:		Omnibus GitLab can be backed up by scheduling a task that runs {{code\|/opt/gitlab/bin/gitlab-rake gitlab:backup:create}}. The destination is configured based on the {{code\|gitlab_rails['backup_path']}} value in {{code\|/etc/gitlab/gitlab.rb}}. Specific components can be skipped by passing in the {{code\|SKIP}} value. For example:
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	# /opt/gitlab/bin/gitlab-rake gitlab:backup:create SKIP=registry,pages,artifacts,builds DIRECTORY=daily		# /opt/gitlab/bin/gitlab-rake gitlab:backup:create SKIP=registry,pages,artifacts,builds DIRECTORY=daily
	}}		}}

	~~The destination is configured based on the {{code\|gitlab_rails['backup_path']}} value in {{code\|/etc/gitlab/gitlab.rb}}.~~

	See Also:		See Also:

Leo: /* Backups */

2019-10-23T22:26:51Z

Backups

← Older revision		Revision as of 22:26, 23 October 2019
Line 173:		Line 173:
	* https://docs.gitlab.com/charts/backup-restore/restore.html		* https://docs.gitlab.com/charts/backup-restore/restore.html

	To restore, run {{code\|gitlab-rake gitlab:backup:restore BACKUP=1571687885_2019_10_21_12.3.5-ee}}, to target a backup file in the backup directory named {{code\|1571687885_2019_10_21_12.3.5-ee_gitlab_backup.tar}}.		To restore, run {{code\|1=gitlab-rake gitlab:backup:restore BACKUP=1571687885_2019_10_21_12.3.5-ee}}, to target a backup file in the backup directory named {{code\|1571687885_2019_10_21_12.3.5-ee_gitlab_backup.tar}}.
			{{highlight\|lang=terminal\|code=
			git@gitlab-task-runner-6c64cd44f8-wvjb4:/srv/gitlab/tmp/backups$ gitlab-rake gitlab:backup:restore BACKUP=1571687885_2019_10_21_12.3.5-ee
			WARNING: This version of GitLab depends on gitlab-shell 10.0.0, but you're running Unknown. Please update gitlab-shell.
			Unpacking backup ...

			}}

	{{Navbox Linux}}[[Category:Linux]]		{{Navbox Linux}}[[Category:Linux]]
	[[Category:Docker]]		[[Category:Docker]]
	[[Category:Todo]]		[[Category:Todo]]

Leo: /* Backups */

2019-10-23T22:26:17Z

Backups

← Older revision		Revision as of 22:26, 23 October 2019
Line 172:		Line 172:
	* https://docs.gitlab.com/omnibus/settings/backups.html		* https://docs.gitlab.com/omnibus/settings/backups.html
	* https://docs.gitlab.com/charts/backup-restore/restore.html		* https://docs.gitlab.com/charts/backup-restore/restore.html

			To restore, run {{code\|gitlab-rake gitlab:backup:restore BACKUP=1571687885_2019_10_21_12.3.5-ee}}, to target a backup file in the backup directory named {{code\|1571687885_2019_10_21_12.3.5-ee_gitlab_backup.tar}}.

	{{Navbox Linux}}[[Category:Linux]]		{{Navbox Linux}}[[Category:Linux]]
	[[Category:Docker]]		[[Category:Docker]]
	[[Category:Todo]]		[[Category:Todo]]

Leo: /* Backups */

2019-10-21T18:04:49Z

Backups

← Older revision		Revision as of 18:04, 21 October 2019
Line 168:		Line 168:
	The destination is configured based on the {{code\|gitlab_rails['backup_path']}} value in {{code\|/etc/gitlab/gitlab.rb}}.		The destination is configured based on the {{code\|gitlab_rails['backup_path']}} value in {{code\|/etc/gitlab/gitlab.rb}}.

			See Also:
			* https://docs.gitlab.com/ee/raketasks/backup_restore.html
			* https://docs.gitlab.com/omnibus/settings/backups.html
			* https://docs.gitlab.com/charts/backup-restore/restore.html

	{{Navbox Linux}}[[Category:Linux]]		{{Navbox Linux}}[[Category:Linux]]
	[[Category:Docker]]		[[Category:Docker]]
	[[Category:Todo]]		[[Category:Todo]]

Leo: /* Backups */

2019-10-21T18:03:53Z

Backups

← Older revision		Revision as of 18:03, 21 October 2019
Line 159:		Line 159:

	== Backups ==		== Backups ==
	GitLab using the Helm Chart can be backed up by running {{code\|backup-~~tuility~~}} inside the ~~gitlab~~ runner container. Backups that are generated will be placed at {{code\|/srv/gitlab/tmp/~~backup_tars~~}} ~~(?? failed only?)~~		GitLab using the Helm Chart can be backed up by running {{code\|backup-utility}} inside the GitLab runner container. Backups that are generated will be placed at {{code\|/srv/gitlab/tmp/backup}} as defined by the {{code\|backup.path}} parameter in {{code\|/srv/gitlab/config/gitlab.yml}}.


	Omnibus GitLab can be backed up by scheduling a task that runs {{code\|/opt/gitlab/bin/gitlab-rake gitlab:backup:create}}. Certain components can be skipped by passing in the {{code\|SKIP}} value. For example:		Omnibus GitLab can be backed up by scheduling a task that runs {{code\|/opt/gitlab/bin/gitlab-rake gitlab:backup:create}}. Certain components can be skipped by passing in the {{code\|SKIP}} value. For example: