3.8 KiB
| stage | group | info |
|---|---|---|
| Systems | Distribution | 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 |
Package information (FREE SELF)
The Omnibus GitLab package is bundled with all dependencies required for GitLab to function correctly. More details can be found at bundling dependencies document.
Package Version
The released package versions are in the format MAJOR.MINOR.PATCH-EDITION.OMNIBUS_RELEASE
| Component | Meaning | Example |
|---|---|---|
MAJOR.MINOR.PATCH |
The GitLab version this corresponds to. | 13.3.0 |
EDITION |
The edition of GitLab this corresponds to. | ee |
OMNIBUS_RELEASE |
The Omnibus GitLab release. Usually, this is 0. This is incremented if we need to build a new package without changing the GitLab version. | 0 |
Licenses
See licensing
Defaults
The Omnibus GitLab package requires various configuration to get the components in working order. If the configuration is not provided, the package uses the default values assumed in the package.
These defaults are noted in the package defaults document.
Checking the versions of bundled software
After the Omnibus GitLab package is installed, all versions of the bundled
libraries are located in /opt/gitlab/version-manifest.txt.
If you don't have the package installed, you can always check the Omnibus GitLab source repository, specifically the configuration directory.
For example, if you examine the 8-6-stable branch, you can conclude that
8.6 packages were running Ruby 2.1.8.
Or, that 8.5 packages were bundled with NGINX 1.9.0.
Signatures of GitLab, Inc. provided packages
Documentation on package signatures can be found at Signed Packages
Checking for newer configuration options on upgrade
Configuration file in /etc/gitlab/gitlab.rb is created on initial installation
of the Omnibus GitLab package. On subsequent package upgrades, the configuration
file is not updated with new configuration. This is done in order to avoid
accidental overwrite of user configuration provided in /etc/gitlab/gitlab.rb.
New configuration options are noted in the
gitlab.rb.template file.
The Omnibus GitLab package also provides convenience command which compares the existing user configuration with the latest version of the template contained in the package.
To view a diff between your configuration file and the latest version, run:
sudo gitlab-ctl diff-config
WARNING:
If you are pasting the output of this command into your
/etc/gitlab/gitlab.rb configuration file, omit any leading + and -
characters on each line.
Init system detection
Omnibus GitLab attempts to query the underlying system in order to
check which init system it uses.
This manifests itself as a WARNING during the sudo gitlab-ctl reconfigure
run.
Depending on the init system, this WARNING can be one of:
/sbin/init: unrecognized option '--version'
when the underlying init system is not upstart.
-.mount loaded active mounted /
when the underlying init system IS systemd.
These warnings can be safely ignored. They are not suppressed because this allows everyone to debug possible detection issues faster.