- I have an MR in
gitlab-org/gitlabproject and want a package or Docker image to test it
- I have an MR in the
omnibus-gitlabproject and want a package or Docker image to test it
- I want to use specific branches or versions of various GitLab components in my build
- Building packages for other OSs
If you are a member of the GitLab team, you will have access to the build infrastructure (or to the colleagues who have access to the infrastructure) and leverage it to build packages.
In the CI pipeline corresponding to your MR, play the
package-and-qa job in
qa stage. This will trigger a downstream pipeline in
QA mirror which
will get you an Ubuntu 16.04 package and an all-in-one Docker image for testing.
It will also run trigger a
gitlab-qa run using these artifacts too.
GitLab project, pipelines running for MRs in
have manual jobs to get a package or Docker image -
Trigger:ee-package, which as their names suggest builds you CE and EE packages
and Docker images, and will perform a QA run.
Versions of the main GitLab components like GitLab-Rails, Gitaly, GitLab Pages,
GitLab Shell, GitLab Workhorse, GitLab Elasticsearch Indexer is controlled by
*_VERSION files in
omnibus-gitlab repository. You can modify these
files to point to your intended targets and the builds will use them. All of
those files accept a branch name, a tag name, or a commit SHA as their content.
They can also be provided via environment variables. Check the table below for
|File name||Environment Variable||Description|
|VERSION||GITLAB_VERSION||Controls Git reference of GitLab Rails application. By default, points to |
|GITALY_SERVER_VERSION||GITALY_SERVER_VERSION||Git reference of the Gitaly repository.|
|GITLAB_PAGES_VERSION||GITLAB_PAGES_VERSION||Git reference of the GitLab Pages repository.|
|GITLAB_SHELL_VERSION||GITLAB_SHELL_VERSION||Git reference of the GitLab Shell repository.|
|GITLAB_WORKHORSE_VERSION||GITLAB_WORKHORSE_VERSION||Git reference of the GitLab Workhorse repository.|
|GITLAB_ELASTICSEARCH_INDEXER_VERSION||GITLAB_ELASTICSEARCH_INDEXER_VERSION||Git reference of the GitLab Elasticsearch Indexer repository. Used only in EE builds.|
|GITLAB_KAS_VERSION||GITLAB_KAS_VERSION||Git reference of the GitLab Kubernetes Agent Server repository.|
If you are running
package-and-qa job from a GitLab MR,
environment variable will be set to the commit SHA corresponding to the pipeline
while other environment variables, if not specified, will be populated from
their corresponding files and passed on to the triggered pipeline.
If you specifically want a package for an OS other than Ubuntu 16.04, or want to
ensure packages can be built with your change on all OSs, you will have to make
omnibus-gitlab’s Release mirror.
A prerequisite for this is access to push branches to
*_VERSIONfiles or environment variables as specified in the above section if needed. You might want to set
eeenvironment variable in the CI config to
trueto use a commit from GitLab repository instead of GitLab-FOSS.
The pipeline will build packages for all supported OSs, and a Docker image.