Skip to content
This repository was archived by the owner on Apr 19, 2021. It is now read-only.

Commit bdf5e6b

Browse files
ghuntleyj0nes2k
andauthored
docs: split prebuild instructions on a per hosting platform basis (#1003)
Co-authored-by: Jonas Kaufmann <[email protected]>
1 parent 64732d9 commit bdf5e6b

File tree

1 file changed

+22
-5
lines changed

1 file changed

+22
-5
lines changed

src/docs/prebuilds.md

Lines changed: 22 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,20 @@ Then, when you do create a new workspace on a branch, or Pull/Merge Request, for
88

99
## Enable Prebuilt Workspaces
1010

11+
### On Bitbucket
12+
13+
To enable prebuilt workspaces for a Bitbucket repository, follow these steps:
14+
15+
1. Allow Gitpod to install repository webhooks, by granting `install webhooks` in [Access Control](https://gitpod.io/access-control/)
16+
2. Trigger a first prebuild manually, by prefixing the repository URL with `gitpod.io/#prebuild/` e.g. like so:
17+
18+
```
19+
gitpod.io/#prebuild/https://bitbucket.org/gitpod-io/gitpod
20+
```
21+
22+
This will [trigger a prebuild](#manual-execution-of-prebuild), and also install a webhook that will trigger new Gitpod prebuilds for every new push to any of your branches to your repository.
23+
24+
1125
### On GitHub
1226

1327
To enable prebuilt workspaces for a GitHub repository, follow these steps:
@@ -16,18 +30,21 @@ To enable prebuilt workspaces for a GitHub repository, follow these steps:
1630
2. Choose the organization or account you wish to install the Gitpod app for, then click `Install`
1731
3. You will be forwarded to Gitpod where you can confirm the installation
1832

19-
### On GitLab and Bitbucket
33+
### On GitLab
2034

21-
To enable prebuilt workspaces for a GitLab or Bitbucket repository, follow these steps:
35+
To enable prebuilt workspaces for a GitLab repository, follow these steps:
2236

23-
1. Allow Gitpod to install repository webhooks, by granting `allow api calls` (GitLab) or `install webhooks` (Bitbucket) in [Access Control](https://gitpod.io/access-control/)
37+
1. Allow Gitpod to install repository webhooks, by granting `allow api calls` in [Access Control](https://gitpod.io/access-control/)
2438
2. Trigger a first prebuild manually, by prefixing the repository URL with `gitpod.io/#prebuild/` e.g. like so:
2539

2640
```
27-
gitpod.io/#prebuild/https://gitlab.com/gitpod/spring-petclinic
41+
gitpod.io/#prebuild/https://gitlab.com/gitpod-io/gitpod
2842
```
2943

30-
This will [trigger a prebuild](#manual-execution-of-prebuild), and also install a webhook that will trigger new Gitpod prebuilds for every new push to your repository. See also [GitLab prebuilds](https://www.gitpod.io/blog/gitlab-support/#prebuilds).
44+
This will [trigger a prebuild](#manual-execution-of-prebuild), and also install a webhook that will trigger new Gitpod prebuilds for every new push to any of your branches to your repository.
45+
46+
If you want to trigger new Gitpod prebuilds for specific branches only, you can configure this in your Gitlab [project settings](https://docs.gitlab.com/ee/user/project/integrations/webhooks.html#branch-filtering).
47+
3148

3249
## Manual execution of prebuild
3350

0 commit comments

Comments
 (0)