Deploying Python repositories contribute
Python Libraries and Utilities
We deploy libraries and utilities to pypi with the gitlab
user using poetry
. Configure the deployment in the pyproject.toml
file:
[tool.poetry]
name = "gitlab-<your package name>"
version = "0.1.0"
description = "<Description of your library/utility>"
authors = ["gitlab"]
readme = "README.md"
packages = [{ include = "<your module>" }]
homepage = ""https://gitlab.com/gitlab/<path/to/repository>"
repository = "https://gitlab.com/gitlab/<path/to/repository>"
Refer to poetry’s documentation for additional configuration options.
The following job can be used to deploy the image. Note that PyPI uses trusted publishers, no keys are necessary when the CI pipeline is configured.
deploy:
stage: deploy
image: python:3.12
script:
- poetry --build publish
rules:
- if: $CI_COMMIT_TAG =~ /^v-/
Python Services
Runway deployment for .com
Services for GitLab.com, GitLab Dedicated and self-hosted customers using CloudConnect are deployed using Runway. Please refer to the project documentation on how to add or manage Runway services.
Deploying in self-hosted environments
Deploying services to self-hosted environments poses challenges as services are not part of the monolith. Currently, Runway does not support self-hosted instances, and Omnibus does not support Python services, so deployment is only possible by users pulling the service image.
Image guidelines
- Use a different user than the root user
- Configure poetry variables correctly to avoid runtime issues
- Use multi-stage Docker builds images to create lighter images
Versioning
Self-hosted customers need to know which version of the service is compatible with their GitLab installation. Python services do not make use of managed versioning, so each service needs to handle its versioning and release cuts.
Per convention, once GitLab creates a new release, it can tag the service repo with a new tag named self-hosted-<gitlab-version>
. An image with that tag is created, as seen on AI Gateway. It’s important that we have a version tag that matches GitLab versions, making it easier for users to deploy the full environment.
Publishing images
Images must be published in the container registry of the project.
It’s also recommend to publish the images on DockerHub. To create an image repository on Docker Hub, create an account with your GitLab handle and create an Access Request to be added to the GitLab organization. Once the image repository is created, make sure the user gitlabcibuild
has read and write access to the repository.
Linux package deployment
To be added.
Deployment on GitLab Dedicated
Deployment of Python services on GitLab Dedicated is not currently supported
Docs
Edit this page to fix an error or add an improvement in a merge request.
Create an issue to suggest an improvement to this page.
Product
Create an issue if there's something you don't like about this feature.
Propose functionality by submitting a feature request.
Feature availability and product trials
View pricing to see all GitLab tiers and features, or to upgrade.
Try GitLab for free with access to all features for 30 days.
Get help
If you didn't find what you were looking for, search the docs.
If you want help with something specific and could use community support, post on the GitLab forum.
For problems setting up or using this feature (depending on your GitLab subscription).
Request support