Products
Create product groups that share repository and pipeline settings.
What this means
A product groups one or more repositories under shared automation settings.
Use products when several repositories belong to the same app, service, customer project, or code area. Pipelines target a repository, but product settings shape how Bilbis names branches, labels MRs/PRs, chooses engines, waits for review, and handles approvals.
When to use it
Create a product when:
- You are setting up the first repository in an organization.
- You want several repositories to share the same pipeline defaults.
- You need product-specific Jira or webhook behavior.
- You want to import repositories from a GitLab or GitHub group.
Before you start
You need owner or admin access to create and edit products.
For a useful product setup, add a Git provider credential first. You can create the product without repositories, but pipelines cannot run until at least one repository is connected.
Field reference
| Field | What it means | Default |
|---|---|---|
| Name | Human-readable product name. | Required |
| Product id | Stable lowercase identifier used in URLs and references. It cannot be changed after creation. | Derived from name |
| Branch prefix | Prefix Bilbis uses for branches it creates. | feat/ |
| MR labels | Labels Bilbis applies to MRs/PRs it opens. | ai-generated |
| Preferred engine | Default engine preference for this product. | Auto |
| Wait for external reviews | How long Bilbis pauses for external review signals before continuing. | Platform default, currently 30 seconds |
| Approval timeout | How long Bilbis waits for approval before timeout behavior applies. | Platform default, currently 1 hour |
| Auto-merge on timeout | Whether Bilbis can merge after approval timeout. | On |
Steps
- Open Products.
- Select New product.
- Enter a name.
- Review the generated product id.
- Adjust branch prefix, MR labels, engine, or approval settings if needed.
- Create the product.
- Add one or more repositories to the product.
What happens next
The product appears in the Products list. Open it to manage repositories, edit product settings, configure Jira overrides, and configure GitLab/GitHub webhook behavior.
Existing pipeline history stays visible even if a product is later deleted, but deleted products and repositories cannot be used for new pipeline runs.
Problems and fixes
| Problem | What to check |
|---|---|
| Product id is rejected | Use lowercase letters, numbers, and dashes only. |
| Product id cannot be edited | Product ids are immutable after creation. Create a new product if the id must change. |
| Pipelines use the wrong branch prefix | Edit the product and update the branch prefix before creating new pipelines. |
| Human approval should always be required | Turn off auto-merge on timeout. |
| Product has no repositories | Add at least one repository before creating a pipeline. |