Source Control

Connect Bitbucket to Odoo via OEC.sh

Connect Bitbucket Cloud or Data Center to deploy Odoo on push.

Available on the Free for Bitbucket Cloud, Pro for Data Center plan.

What this integration does

OEC.sh integrates with Bitbucket Cloud and Bitbucket Data Center (self-hosted). Push and pull request events trigger deploys, while OEC.sh posts build statuses back so your pull request page shows the deploy result inline. Bitbucket Data Center connections require the Pro plan.

The integration is configured from your OEC.sh project settings. If you have not created an account yet, you can start free and connect Bitbucket in under five minutes. Compare OEC.sh against the hosted Odoo.sh option if you are still deciding where to run Odoo.

Common use cases

Atlassian-stack teams that already use Jira and Confluence and want their Odoo code in Bitbucket

Self-hosted Bitbucket Data Center customers who need managed Odoo deploys without leaving their Atlassian estate

Triggering deploys from Bitbucket Pipelines after a CI build passes

Posting deploy statuses back to the Bitbucket pull request page for fast review

How to set it up

Five steps, end to end. Most teams finish in under five minutes.

1
In OEC.sh, go to Settings, Integrations, then click Connect Bitbucket and run the OAuth flow
2
For Bitbucket Data Center, choose 'Self-hosted Bitbucket', add your instance URL, and provide an app password
3
Select the workspace and repository you want to deploy from
4
Map branches to environments and pick the trigger events (push, merge, tag)
5
Optionally add a Bitbucket Pipeline step that calls the OEC.sh Public API for tighter control

Example payload

Here is the exact format OEC.sh sends (or that you would send to OEC.sh, in the case of GitHub Actions, GitLab CI, Bitbucket Pipelines, and n8n).

pipelines:
  branches:
    main:
      - step:
          name: Deploy to OEC.sh
          image: curlimages/curl:latest
          script:
            - |
              curl -X POST https://api.oec.sh/v1/projects/$OECSH_PROJECT_ID/deploy \
                -H "Authorization: Bearer $OECSH_API_TOKEN" \
                -H "Content-Type: application/json" \
                -d "{
                  \"environment\": \"production\",
                  \"commit\": \"$BITBUCKET_COMMIT\",
                  \"branch\": \"$BITBUCKET_BRANCH\"
                }"

Try this with a free account

Plan availability

Bitbucket Cloud works on Free ($0/mo). Bitbucket Data Center (self-hosted) requires Pro ($39/mo) and above.

See full pricing

Frequently Asked Questions

No. Bitbucket Cloud Free works for OEC.sh's standard integration. Bitbucket Data Center (self-hosted) is paid Atlassian software, but the OEC.sh side does not require any additional Bitbucket licence.

Bitbucket Cloud uses OAuth via the Atlassian login. Bitbucket Data Center uses an app password and your instance URL. Both are configured under Settings, Integrations in the OEC.sh dashboard.

Yes. The commit status message, PR comment text, and deploy URL format are all configurable per repository under Settings, Integrations, Bitbucket. You can also disable status posting if you only want OEC.sh to listen for push events.

Bitbucket Cloud works on Free ($0/mo). Bitbucket Data Center (self-hosted) requires Pro ($39/mo) and above.

Yes. Bitbucket Data Center (the self-hosted version) is supported on the Pro plan ($39/mo) and above. You connect using an app password and your instance URL. Bitbucket Cloud users do not need a paid plan to connect.