2020-07-23 11:09:28 -04:00
---
2022-05-29 20:08:35 -04:00
stage: Systems
2020-07-23 11:09:28 -04:00
group: Distribution
2020-11-26 01:09:20 -05:00
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-07-23 11:09:28 -04:00
---
2017-05-05 04:41:16 -04:00
# Building a package for testing
While developing a new feature or modifying an existing one, it is helpful if an
2020-05-27 05:08:30 -04:00
installable package (or a Docker image) containing those changes is available
2017-05-05 04:41:16 -04:00
for testing. For this very purpose, a manual job is provided in the GitLab CI/CD
2019-08-27 04:44:07 -04:00
pipeline that can be used to trigger a pipeline in the Omnibus GitLab repository
2018-11-12 19:39:21 -05:00
that will create:
- A deb package for Ubuntu 16.04, available as a build artifact, and
2022-08-07 23:09:21 -04:00
- A Docker image, which is pushed to the
[Omnibus GitLab container registry ](https://gitlab.com/gitlab-org/omnibus-gitlab/container_registry )
2019-11-25 19:06:28 -05:00
(images titled `gitlab-ce` and `gitlab-ee` respectively and image tag is the
2018-11-12 19:39:21 -05:00
commit which triggered the pipeline).
2017-05-05 04:41:16 -04:00
2019-08-27 04:44:07 -04:00
When you push a commit to either the GitLab CE or GitLab EE project, the
2017-05-05 04:41:16 -04:00
pipeline for that commit will have a `build-package` manual action you can
trigger.
2019-11-25 19:06:28 -05:00
![Manual actions ](img/build_package_v12_6.png )
2017-05-09 11:53:23 -04:00
2019-11-25 19:06:28 -05:00
![Build package manual action ](img/trigger_build_package_v12_6.png )
2017-05-09 11:53:23 -04:00
2017-05-05 04:41:16 -04:00
## Specifying versions of components
If you want to create a package from a specific branch, commit or tag of any of
2021-07-22 14:08:29 -04:00
the GitLab components (like GitLab Workhorse, Gitaly, or GitLab Pages), you
2020-06-09 23:08:17 -04:00
can specify the branch name, commit SHA or tag in the component's respective
2017-05-05 04:41:16 -04:00
`*_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-08-27 04:44:07 -04:00
## Specifying the branch in Omnibus GitLab repository
2017-05-05 04:41:16 -04:00
2019-08-27 04:44:07 -04:00
In scenarios where a configuration change is to be introduced and Omnibus GitLab
2017-05-05 04:41:16 -04:00
repository already has the necessary changes in a specific branch, you can build
2021-02-25 13:11:05 -05:00
a package against that branch through a CI/CD variable named
`OMNIBUS_BRANCH` . To do this, specify that variable with the name of
2017-05-05 04:41:16 -04:00
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.