With Gitpod you can describe your development environment as code to get fully set up, compiled, and tested development environments for any GitLab project. The development environments are not only automated but also prebuilt which means that Gitpod continuously builds your Git branches like a CI/CD server.
This means you don’t have to wait for dependencies to be downloaded and builds to finish, you can start coding immediately. With Gitpod you can start coding instantly on any project, branch, and merge request from any device, at any time, from your browser:
To use the GitLab Gitpod integration, it must be enabled for your GitLab instance. Users of:
- GitLab.com can use it immediately after it’s enabled in their user settings.
- GitLab self-managed instances can use it after:
With the Gitpod integration enabled for your GitLab instance, to enable it for yourself:
- In the top-right corner, select your avatar.
- Select Preferences.
- Under Preferences, locate the Integrations section.
- Select the Enable Gitpod integration checkbox and select Save changes.
For GitLab self-managed instances, a GitLab administrator needs to:
- Set up a Gitpod instance to integrate with GitLab. Refer to the Gitpod documentation to get your instance up and running.
- Enable it in GitLab:
- On the top bar, select Menu > Admin.
- On the left sidebar, select Settings > General.
- Expand the Gitpod configuration section.
- Select the Enable Gitpod integration checkbox.
- Add your Gitpod instance URL (for example,
- Select Save changes.
Your users can then enable it for themselves.
You can launch Gitpod directly from GitLab in one of these ways:
- From your project’s page:
- From a merge request:
Gitpod builds your development environment for your branch.