debian-mirror-gitlab/doc/development/build_test_package.md

47 lines
2.2 KiB
Markdown
Raw Normal View History

2020-10-24 23:57:45 +05:30
---
2022-07-23 23:45:48 +05:30
stage: Systems
2020-10-24 23:57:45 +05:30
group: Distribution
2021-02-22 17:27:13 +05:30
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2020-10-24 23:57:45 +05:30
---
2017-08-17 22:00:37 +05:30
# Building a package for testing
While developing a new feature or modifying an existing one, it is helpful if an
2020-06-23 00:09:42 +05:30
installable package (or a Docker image) containing those changes is available
2017-08-17 22:00:37 +05:30
for testing. For this very purpose, a manual job is provided in the GitLab CI/CD
2019-12-04 20:38:33 +05:30
pipeline that can be used to trigger a pipeline in the Omnibus GitLab repository
2019-02-15 15:39:39 +05:30
that will create:
- A deb package for Ubuntu 16.04, available as a build artifact, and
2022-08-27 11:52:29 +05:30
- A Docker image, which is pushed to the
[Omnibus GitLab container registry](https://gitlab.com/gitlab-org/omnibus-gitlab/container_registry)
2020-01-01 13:55:28 +05:30
(images titled `gitlab-ce` and `gitlab-ee` respectively and image tag is the
2019-02-15 15:39:39 +05:30
commit which triggered the pipeline).
2017-08-17 22:00:37 +05:30
2019-12-04 20:38:33 +05:30
When you push a commit to either the GitLab CE or GitLab EE project, the
2017-08-17 22:00:37 +05:30
pipeline for that commit will have a `build-package` manual action you can
trigger.
2020-01-01 13:55:28 +05:30
![Manual actions](img/build_package_v12_6.png)
2017-09-10 17:25:29 +05:30
2020-01-01 13:55:28 +05:30
![Build package manual action](img/trigger_build_package_v12_6.png)
2017-09-10 17:25:29 +05:30
2017-08-17 22:00:37 +05:30
## Specifying versions of components
If you want to create a package from a specific branch, commit or tag of any of
2021-10-27 15:23:28 +05:30
the GitLab components (like GitLab Workhorse, Gitaly, or GitLab Pages), you
2020-06-23 00:09:42 +05:30
can specify the branch name, commit SHA or tag in the component's respective
2017-08-17 22:00:37 +05:30
`*_VERSION` file. For example, if you want to build a package that uses the
branch `0-1-stable`, modify the content of `GITALY_SERVER_VERSION` to
`0-1-stable` and push the commit. This will create a manual job that can be
used to trigger the build.
2019-12-04 20:38:33 +05:30
## Specifying the branch in Omnibus GitLab repository
2017-08-17 22:00:37 +05:30
2019-12-04 20:38:33 +05:30
In scenarios where a configuration change is to be introduced and Omnibus GitLab
2017-08-17 22:00:37 +05:30
repository already has the necessary changes in a specific branch, you can build
2021-04-17 20:07:23 +05:30
a package against that branch through a CI/CD variable named
`OMNIBUS_BRANCH`. To do this, specify that variable with the name of
2017-08-17 22:00:37 +05:30
the branch as value in `.gitlab-ci.yml` and push a commit. This will create a
manual job that can be used to trigger the build.