Gitlab Master FAQ - Revision history

Mri083: /* Stop docker container */ docker container needs to be stopped before it can be removed

2021-03-10T10:18:50Z

Stop docker container: docker container needs to be stopped before it can be removed

← Older revision		Revision as of 10:18, 10 March 2021
Line 50:		Line 50:

	==== Stop docker container ====		==== Stop docker container ====
	Stop, note that container will not be deleted		Stop, note that container will not be deleted, but it disappears from the list of active containers, use <code>--all</code> to list all containers
	docker container stop gitlab-runner-projectname		docker container stop gitlab-runner-projectname

	If it ~~should~~ be removed~~, this needs to be explicitly done (also in one go without stop)~~		Once the container is stopped, it can also be removed:
	docker container rm gitlab-runner-projectname		docker container rm gitlab-runner-projectname

	~~Can also~~ be restarted		or, it can be restarted again:
	docker container stop gitlab-runner-projectname		docker container stop gitlab-runner-projectname

Mri083: /* Stop docker container */

2021-03-10T10:15:16Z

Stop docker container

← Older revision		Revision as of 10:15, 10 March 2021
Line 58:		Line 58:
	Can also be restarted		Can also be restarted
	docker container stop gitlab-runner-projectname		docker container stop gitlab-runner-projectname

			==== Limit number of cores used by the runner ====
			Use option <code>--cpuset-cpus</code> to assign dedicated CPUs to the container. There is also an option <code>--cpus</code> to specify a fraction of cores to be used, but this will not effect the <code>nproc</code> command in the container.

			To utilize all but 2 cores of the host system, e.g. start with the calculated value:
			cpus=`nproc`; docker run --cpuset-cpus="0-$((cpus - 3))" ...

			In the container, the <code>nproc</code> command can be used to retrieve the number number of cores, e.g. to pass it to the build system.

	=== Importing an external package ===		=== Importing an external package ===

Mri083: /* Setup GitLab CI */

2021-03-10T09:17:26Z

Setup GitLab CI

@@ Line 22: / Line 22: @@
 Example link
      https://oauth2@git.app.uib.no/pct/development/pct-online
 === Importing an external package ===

Mri083: Adding instructions how to mirror a repository

2021-03-04T13:52:56Z

Adding instructions how to mirror a repository

← Older revision		Revision as of 13:52, 4 March 2021
Line 4:		Line 4:

	Please '''edit''' this page and '''add''' your question, or send email to pCT@uib.no		Please '''edit''' this page and '''add''' your question, or send email to pCT@uib.no

			=== Mirror a repository ===
			GitLab supports mirroring of a repository, the GitLab version provided by UiB supports mirroring by ''push''. That means, repository content is pushed to another repository.

			The set this up
			# Create a R/W repository access token in the target repository
			# In the source repository choose '''Settings''' -> '''Repository''' and expand '''Mirroring repositories'''
			#: '''Git repository URL''': https://oauth2@git.app.uib.no/group/project
			#: '''Mirror direction''': Push (this is fixed in the current version of GitLab)
			#: '''Authentication method''': Password (this is fixed in the current version of GitLab)
			#: '''Password''': the access token
			# Choose options, whether to prohibit diverging refs, and which branches to mirror. In most cases the mirroring should not be done for all branches but only the protected ones (which represent the stable development).
			# Click <span style="color:white; background:green; border:solid 2px green">'''Mirror repository'''</span>

			GitLab takes care of automatically pushing changes to mirror repository. Alternatively, update can be triggered from the Web interface

			Example link
			https://oauth2@git.app.uib.no/pct/development/pct-online

	=== Importing an external package ===		=== Importing an external package ===

Mri083 at 10:24, 10 February 2021

2021-02-10T10:24:22Z

← Older revision		Revision as of 10:24, 10 February 2021
Line 4:		Line 4:

	Please '''edit''' this page and '''add''' your question, or send email to pCT@uib.no		Please '''edit''' this page and '''add''' your question, or send email to pCT@uib.no

			=== Importing an external package ===
			The project will use a couple of external packages which are hosted in a different master repository. Copies of such external packages can be added to the gitlab server under our project group to provide a consistent package.

			Here is a proposed workflow for importing a package which is already hosted in git.
			# Create new repository in the pCT group or ask for creation, lets call it ''newPackage''
			# Fork the repository to your user space
			# Clone the package you want to import
			#:<pre> git clone <some_external_link> newPackage # we give it the new name</pre>
			#:<pre> cd newPackage</pre>
			# Redirect upstream URL to the fork in your gitlab user space
			#:<pre> git remote set-url origin https://user@gitlab.uib.no/user/newPackage.git</pre>
			# Now make a forced push (option ''-f'') to import the repository to your fork
			#:<pre> git push -f origin</pre>
			# Create merge request to branch ''import'' (if not existing, ''master'' or any other appropriate branch) by following the instructions [[Documentation#Pull/Merge request \| Pull/Merge request]]

Mri083: Created page with "Main Page -> Documentation -> Gitlab Master FAQ This is a collection of frequently asked Gitlab questions for project maintainers Please '''edit''' this page and..."

2017-01-26T12:27:54Z

Created page with "Main Page -> Documentation -> Gitlab Master FAQ This is a collection of frequently asked Gitlab questions for project maintainers Please '''edit''' this page and..."

New page

[[Main Page]] -> [[Documentation]] -> [[Gitlab Master FAQ]]

This is a collection of frequently asked Gitlab questions for project maintainers

Please '''edit''' this page and '''add''' your question, or send email to pCT@uib.no