GitLab is a single application for the entire DevOps lifecycle. This makes GitLab unique and makes Concurrent DevOps possible, unlocking your organization from the constraints of a pieced together toolchain. Join us for a live Q&A to learn how GitLab can give you unmatched visibility and higher levels of efficiency in a single application across the DevOps lifecycle.
This charm provides the GitLab code hosting and CI/CD platform, for use with MySQL as a backend database.
Optionally, a reverse proxy can be placed in front of GitLab by relating this charm to a charm implementing the
Running the following step will install the GitLab Omnibus package,
with default configuration.
juju deploy gitlab
Before GitLab can be used, you will need to relate it to a
PostgreSQL cluster via the db-admin relation:
juju add-relation gitlab:pgsql postgresql:db-admin
Usage via HTTPS can be achieved by running GitLab behind a reverse
proxy that has been properly configured for the desired external
domain name. A good default reverse proxy is provided by the
juju add-relation gitlab:reverseproxy haproxy
GitLab has a fairly strict upgrade policy due to the required
DB migrations which are run on package upgrade. Due to this,
this package will upgrade the package periodically to make sure
that no upgrade steps are missed. If you would like to control
this process manually, you can set a specific package version
you would like to stay on using the
upgrade action can then be run when you do want to
upgrade. Unset the
version option and then run the
action to upgrade to the latest version, or set a new desired
version in the
version option and then run the
action to upgrade to a new specified version.
This charm (and GitLab) previously supported installation to a MySQL database. If you had deployed this charm against MySQL, you must migrate to PostgreSQL to keep using it, as GitLab has deprecated support for MySQL as of the 12.1 release. Deploying with MySQL is unsupported, as GitLab no longer actually works with MySQL as a backend DB.
NOTE: There is a chance the following process could nuke your
database contents. Or mess up your schema. Always back up your
MySQL database prior to running the
If you have data in your PostgreSQL database, you should back
that up too, as the migration will very likely remove it if
there is already a gitlab database there.
ALSO NOTE: The migration and schema manipulation in upstream
GitLab is fragile. Given the official guidance is to upgrade
before upgrading to 12.1, if you have already upgraded or have
not upgraded in a while prior to attempting the migration, you
will need to carefully control the upgrade process (per the
above process) until you reach version 12.0.9, perform the
migration, and then continue any other upgrades. Failure to do
so will get your MySQL database schema and upgrade out of date.
The charm has some safety in place, as if you are on the latest
charm, and have MySQL related, it will cease upgrades and
reconfigurations. You can run both manually as you upgrade using
reconfigure actions which relate directly to
the apt package upgrades and
gitlab-ctl reconfigure calls in
the upstream migration
In order to migrate, deploy a new
cs:postgresql unit or cluster, and
db-admin relation from the PostgreSQL charm to this
pgsql relation. Do not remove the MySQL relation yet, as
the MySQL credentials will be stored in the charm's key/value
store and used to migrate data from the old database. Once the
relation to PostgreSQL is healthy, you can use the
action to migrate your data using
pgloader. Once this is complete,
remove the MySQL relation, and GitLab will be reconfigured to use
the new PostgreSQL database. Migrations will run automatically.
If there is any issue with the migration process, the charm will
enter error state - the charm
debug-log will be helpful in
determining the problem, and manual intervention will likely be
required. If all goes well, no further action will be required
to continue using PostgreSQL.
This charm is written by James Hebden of the Pirate Charmers group.
- configuration of SMTP settings
- administrative password management via juju config
- specify option to pass hostname over reverseproxy relation
- specify option to override address used for reverseproxy
- interface for relating GitLab CI runners (WIP)
- (string) The APT signing key used for the repository specified by apt_repo
- (string) The APT source repository to configure before installing GitLab. The Ubuntu distribution, component, /ubuntu suffix, as well as package type (gitlab-ce/gitlab-ee) will be appended. e.g. gitlab-ce/ubuntu bionic main
- (string) The external URI of this GitLab install. This will be used to configure GitLab, and any reverse proxy configured via the reverseproxy relation. Defaults to the fqdn of the unit.
- (int) The HTTP port the GitLab backend will listen for connections on. It is recommended to relate this charm to a reverse proxy, rather than customising this value
- (string) The package to use. Options are gitlab-ce for the FOSS version of gitlab-ee for the Enterprise Edition.
- (int) The external TCP port over which SSH-based git clone operations will be available, when GitLab is related to an external load balancer via the reverseproxy relation. Without a reverseproxy relation, the system sshd is used on port 22.
- (string) The version of GitLab to install. Defaults (when this setting is empty) to latest.