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.
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:
- Select your avatar in the top-right corner, then select Settings > Preferences.
- Under Integrations, locate the Gitpod section.
- Check the Enable Gitpod integration checkbox and select the Save changes button.
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:
- Go to Admin Area > Settings > General.
- Expand the Gitpod configuration section.
- Check the Enable Gitpod integration checkbox.
- Add your Gitpod instance URL (for example,
- Select the Save changes button.
Your users then need to enable it for themselves.
You can launch Gitpod directly from GitLab by clicking the Gitpod button from the Web IDE dropdown on the project page:
A project launched in GitLab looks like: