Heads up!
On October 1, we introduced Gitpod Flex. You can swap between documentation by using the
switcher in the left navigation bar.
Add an SCM integration for GitHub, GitLab or Bitbucket
Integrate it with your SCM as per the steps shown in the UI or below. You can now create your first workspace and start using Gitpod! For more information on how to use Gitpod, please see the Getting Started guide of Gitpod.
- Look at these steps for information on how to integrate
GitLab.com
with your Gitpod instance. You will need to entergitlab.com
as theProvider Host Name
in the New Git Integration Modal if you want to use gitlab.com, contrary to what is described. - Look at these these steps for information on how to integrate
GitHub.com
with your Gitpod instance. You will need to entergithub.com
as theProvider Host Name
in the New Git Integration Modal if you want to use github.com, contrary to what is described. - Look at these steps for information on how to integrate
Bitbucket Server
with your Gitpod instance. SelectBitbucket Server
as theProvider Type
in the New Git Integration Modal. For bitbucket.org this requires configuring an “OAuth consumer” on a “workspace”. This is slightly different from the documented Bitbucket Server integration. See gitpod PR #9894 for an example.
The first workspace start(s) will take longer than usual, sometimes exceeding 10 minutes depending on the workspace image used. This is because an image first needs to be built, a node needs to be spun up, and that image then downloaded to the node. However, subsequent workspace starts will be significantly faster.