GitLab CI - Revision history

Kai: /* How to create Product Releases with Binaries */

2021-06-24T08:29:23Z

How to create Product Releases with Binaries

← Older revision		Revision as of 2021-06-24T08:29:23
Line 95:		Line 95:
	= How to create Product Releases with Binaries =		= How to create Product Releases with Binaries =

	In GitLab, a release can be created from a tagged version of the repository. ~~By uploading binary release~~ assets (for example, a built and packaged product) as a [https://docs.gitlab.com/ee/user/packages/generic_packages generic ~~package~~], the ~~binary asset~~ can be ~~attached to~~ the ~~release. The~~ most convenient way of obtaining permissions from the GitLab server for uploading ~~the~~ binary ~~asset into the generic packages repository, which is separate from the project sources repository~~, is during the execution of a CI job. After uploading the asset, the same CI ~~script requests~~ the creation of a ~~[https://docs.gitlab.com/ee/user/project/releases/index.html~~ release] that includes the uploaded asset.		In GitLab, a [https://docs.gitlab.com/ee/user/project/releases/index.html release] can be created from a tagged version of the repository. Binary assets (for example, a pre-built and packaged product) can be made part of a release after uploading the assets into the [https://docs.gitlab.com/ee/user/packages/generic_packages generic packages] repository, which is separate from the project sources repository. Uploading into the generic packages repository requires special permissions for which you would normally generate special access tokens (which can be used in a ''curl'' command). However, the most convenient way of obtaining permissions from the GitLab server for uploading binary assets, is during the execution of a CI job, where a special access token is handed to the CI runner from the GitLab server. After uploading the asset, the same CI runner will then request the creation of a release that includes the uploaded asset.

	* In the project root folder, add a ''.gitlab-ci.yml'' file with the contents based on the example below. Note that the upload script makes use of CI_JOB_TOKEN, which GitLab passes to the build runner for use in build scripts that need to authenticate themselves when sending files to GitLab.<br/>		* In the project root folder, add a ''.gitlab-ci.yml'' file with the contents based on the example below. Note that the upload script makes use of CI_JOB_TOKEN, which GitLab passes to the build runner for use in build scripts that need to authenticate themselves when sending files to GitLab.<br/>

Kai at 2021-06-24T07:55:35

2021-06-24T07:55:35Z

← Older revision		Revision as of 2021-06-24T07:55:35
Line 1:		Line 1:
	~~= CI/CD Pipeline Configuration =~~		In addition to being a Git repository service, GitLab provides Continuous Integration features.

	GitLab CI~~/CD build~~ for a repository ~~are controlled~~ placing a file named '''.gitlab_ci.yml''' in the root folder of the repository. The ~~expected content~~ of the file ~~is specified on~~ GitLab's		= CI Pipeline Configuration =
	[https://docs.gitlab.com/ee/ci/yaml/gitlab_ci_yaml.html gitlab_ci.yml ~~Documentation~~ page].
			A GitLab CI pipeline for a repository is established by placing a file named '''.gitlab_ci.yml''' in the root folder of the repository. The contents of the file specify the structure and the actions of the pipeline. See GitLab's [https://docs.gitlab.com/ee/ci/yaml/gitlab_ci_yaml.html gitlab_ci.yml documentation page] to see what's possible.

	= GitLab Runner =		= GitLab Runner =
			GitLab Runner is GitLab's own solution for a background service that can be hosted separately from the GitLab server and is responsible for executing the CI pipeline.

	== Installing ==		== Installing ==

Kai: Kai moved page GitLab to GitLab CI without leaving a redirect: the content is specific to the Continuous Integration features of GitLab

2021-06-24T07:44:51Z

Kai moved page GitLab to GitLab CI without leaving a redirect: the content is specific to the Continuous Integration features of GitLab

← Older revision	Revision as of 2021-06-24T07:44:51
(No difference)

Kai: /* How to create Product Releases with Binaries */

2021-06-24T07:21:36Z

How to create Product Releases with Binaries

← Older revision		Revision as of 2021-06-24T07:21:36
Line 93:		Line 93:
	= How to create Product Releases with Binaries =		= How to create Product Releases with Binaries =

	~~The best way to add binaries to project releases on~~ GitLab, ~~is to create~~ a ~~job which uploads~~ the release assets as a [https://docs.gitlab.com/ee/user/packages/generic_packages generic package], ~~then creates~~ a [https://docs.gitlab.com/ee/user/project/releases/index.html release] ~~by referring to~~ the uploaded ~~assets~~.		In GitLab, a release can be created from a tagged version of the repository. By uploading binary release assets (for example, a built and packaged product) as a [https://docs.gitlab.com/ee/user/packages/generic_packages generic package], the binary asset can be attached to the release. The most convenient way of obtaining permissions from the GitLab server for uploading the binary asset into the generic packages repository, which is separate from the project sources repository, is during the execution of a CI job. After uploading the asset, the same CI script requests the creation of a [https://docs.gitlab.com/ee/user/project/releases/index.html release] that includes the uploaded asset.

	* In the project root folder, add a ''.gitlab-ci.yml'' file with the contents based on the example below. Note that the upload script makes use of CI_JOB_TOKEN, which GitLab passes to the build runner for use in build scripts that need to authenticate themselves when sending files to GitLab.<br/>		* In the project root folder, add a ''.gitlab-ci.yml'' file with the contents based on the example below. Note that the upload script makes use of CI_JOB_TOKEN, which GitLab passes to the build runner for use in build scripts that need to authenticate themselves when sending files to GitLab.<br/>

Kai at 2021-06-23T18:28:29

2021-06-23T18:28:29Z

← Older revision		Revision as of 2021-06-23T18:28:29
Line 134:		Line 134:
	cp main /usr/local/bin/release-cli		cp main /usr/local/bin/release-cli
	</pre>		</pre>
	* Create the binary to be released and place it in the folder expected by the upload script. ~~You may want to set up~~ a VirtualBox shared folder.		* Create the binary to be released and place it in the folder expected by the upload script. When using a VirtualBox shared folder, make sure the user ''gitlab-runner'' is in the ''vboxsf'' group.
			<pre class="terminal">
			sudo usermod -a -G vboxsf gitlab-runner
			</pre>
	* In GitLab, create a tag for the version to be released. This will trigger the execution of the upload job in GitLab Runner.		* In GitLab, create a tag for the version to be released. This will trigger the execution of the upload job in GitLab Runner.
	* ~~To refer the user to a~~ download page containing all releases~~, use the following URL:~~		* The download page containing all releases will be at
	<pre class="code">		<pre class="code">
	https://gitlab.com/<project group name>/<project name>/-/releases		https://gitlab.com/<project group name>/<project name>/-/releases
	</pre>		</pre>

Kai at 2021-06-23T18:16:20

2021-06-23T18:16:20Z

@@ Line 1: / Line 1: @@
-= Pipeline Configuration File =
+= CI/CD Pipeline Configuration =
 GitLab CI/CD build for a repository are controlled placing a file named '''.gitlab_ci.yml''' in the root folder of the repository. The expected content of the file is specified on GitLab's
@@ Line 85: / Line 85: @@
 Note that the '''pull_policy''' option was explicitly set to "never" instead of going with the default "always". This prevents GitLab Runner from searching for the specified Docker image on [https://hub.docker.com Docker Hub] and directs the query to the local docker engine!
-= How To Create A Product Release =
+= How to create a Product Webpage =

Kai at 2021-06-23T17:02:52

2021-06-23T17:02:52Z

@@ Line 1: / Line 1: @@
-== Pipeline Configuration File ==
+= Pipeline Configuration File =
 GitLab CI/CD build for a repository are controlled placing a file named '''.gitlab_ci.yml''' in the root folder of the repository. The expected content of the file is specified on GitLab's
 [https://docs.gitlab.com/ee/ci/yaml/gitlab_ci_yaml.html gitlab_ci.yml Documentation page].
-== GitLab Runner ==
+= GitLab Runner =
-== Creating a Product Release ==
+[session_server]

Kai: Created page with "== Pipeline Configuration File == GitLab CI/CD build for a repository are controlled placing a file named '''.gitlab_ci.yml''' in the root folder of the repository. The expec..."

2021-06-23T17:01:11Z

Created page with "== Pipeline Configuration File == GitLab CI/CD build for a repository are controlled placing a file named '''.gitlab_ci.yml''' in the root folder of the repository. The expec..."

New page

== Pipeline Configuration File ==

GitLab CI/CD build for a repository are controlled placing a file named '''.gitlab_ci.yml''' in the root folder of the repository. The expected content of the file is specified on GitLab's
[https://docs.gitlab.com/ee/ci/yaml/gitlab_ci_yaml.html gitlab_ci.yml Documentation page].

== GitLab Runner ==

== Creating a Product Release ==