Import your Bitbucket Cloud repositories
Astrolabe reads the catalog-info.yaml file of the repositories of your Bitbucket Cloud workspace and adds
them to the catalog.
You set it up once, as an administrator.
Before you start
The catalog reads Bitbucket Cloud with the token of the Bitbucket Cloud integration. Add it first: see Add the Bitbucket Cloud integration.
Until it is added, the Bitbucket Cloud card of Administration › Catalog is greyed out, with Configure the bitbucketCloud integration first: without it, this provider cannot read anything.
🔧 Configure the Bitbucket Cloud provider
-
In the left sidebar, at the bottom, click Administration.
-
Under PLATFORM, click Catalog. The Providers tab opens.
-
On the Bitbucket Cloud card, click Configure.
-
In Workspace, enter your workspace, as in
https://bitbucket.org/<workspace>. For exampleacme. -
Click Install.
The window Reloading configuration says Please wait while the instance is reloading.... Then the page comes back.
Hover the ? next to a field to see what it expects, with an example.
The other fields
| Field | What it does |
|---|---|
| Catalog Path | Where the descriptor file sits in each repository. Default: /catalog-info.yaml. |
| Project Key Regex | Only the projects whose key matches are imported, for example ^team-.*. Empty: all of them. |
| Repo Slug Regex | Only the repositories whose slug matches are imported, for example ^team-.*. Empty: all of them. |
| Repositories Per Page | How many repositories Astrolabe asks Bitbucket Cloud for at a time. Empty: Bitbucket's default. |
▶️ Run the collection now
The catalog reads Bitbucket Cloud every 30 minutes. You don't want to wait?
-
On Administration › Catalog, find the Catalog collection table.
-
On the Bitbucket Cloud row, click Run the Bitbucket Cloud collection now in the Actions column.
-
Wait half a minute, then reload the page. State shows the result of the run, and Detail says why when it failed.
Your repositories are then in Catalog. This step was not checked on a live instance.
✅ That's it!