Bitbucket Pipelines adapter
Reference for the Bitbucket Pipelines adapter. Webhook events, signature verification, status mapping and limits.
The Bitbucket adapter turns Bitbucket Cloud build status events into Prodgator runs. To set it up, see Connect Bitbucket.
Events
| Bitbucket event () | Prodgator record |
|---|---|
| Pipeline run | |
| Pipeline run update |
Each Bitbucket Pipelines build posts a commit status, and Prodgator records one run per repository and status key. Other events are acknowledged and dropped.
Webhook verification
Each connection has its own webhook URL, , and its own secret. Bitbucket sends . Prodgator recomputes it with the connection's secret and answers if it does not match.
Status mapping
| Bitbucket state | Prodgator status | Pipelines tab |
|---|---|---|
| Queued | ||
| Running | ||
| Awaiting approval | ||
| Success | ||
| , | Failed | |
| Failed | ||
| Cancelled | ||
| Cancelled |
Field mapping
| Bitbucket field | Prodgator field |
|---|---|
| + | Run ID |
| Workflow name | |
| Branch | |
| Commit | |
| Link to the build, and the build number | |
| Repository | |
| Actor |
Duration is the time between the status being created and last updated.
Steps and logs
When you open a run, Prodgator reads the pipeline's steps and step logs from the Bitbucket API with the connection's token. Parallel steps show as separate steps.
Cancel a run
People who can re-run runs (Developers, Release managers and Org admins) can stop a running pipeline with Cancel run. Prodgator calls the Bitbucket stop-pipeline endpoint with the connection's token, which needs the Pipelines: Write permission. The Prodgator audit log records who clicked.
Bitbucket has no API to run a pipeline step again, so Re-run failed jobs and per-job Re-run are not offered for Bitbucket. Use Rerun failed steps in Bitbucket.
A connection made before this action existed may lack the permission. The action then fails with a message asking you to reconnect Bitbucket in Organization > Integrations.
Deployment gate
Bitbucket's API cannot approve or run a paused step, so a deployment step that should wait for Prodgator runs the pipe in gate mode. The pipe uses two public endpoints:
| Request | Authentication | What it does |
|---|---|---|
| The step's OIDC token () | Opens the gate for the step's deployment environment: the deployment becomes pending approval under Prodgator's protection rule. Returns the gate id, the decision so far and a poll token. | |
| poll token | Returns (, , or ), who decided and their note. |
The poll token is valid for 12 hours, because the OIDC token expires while the step waits. Prodgator stores only its SHA-256 hash. A step that is not a deployment step (no ) is refused with . While the gate is open, Bitbucket reports the step as running; Prodgator keeps the deployment pending until it is answered.
Limits
- Deployment steps are approved from Prodgator only when they run the gate. See Approve deployments from Prodgator.
- The commit message is not included in build status events, so it is not shown.
Jenkins adapter (beta)
Reference for the Jenkins adapter. Request format, signature, status mapping and limits.
Azure Pipelines adapter
Reference for the Azure DevOps adapter. What Prodgator supports for Azure Pipelines and Azure Repos, the permissions it asks for, the Prodgator gate, run reports and what is not available.