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
|
|
|
|
installable package (or a docker image) containing those changes is available
|
|
|
|
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
|
|
|
|
- A docker image, which is pushed to [Omnibus GitLab's 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
|
|
|
|
the GitLab components (like GitLab Workhorse, Gitaly, GitLab Pages, etc.), you
|
|
|
|
can specify the branch name, commit sha or tag in the component's respective
|
|
|
|
`*_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
|
|
|
|
a package against that branch through an environment variable named
|
|
|
|
`OMNIBUS_BRANCH`. To do this, specify that environment variable with the name of
|
|
|
|
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.
|