Bitbucket Pipelines is the CI/CD service built into Atlassian's Bitbucket Cloud, billed in build minutes with optional self-hosted runners; these pages cover replacing it with self-hosted Woodpecker CI, Jenkins or GitLab CI/CD.
Compares Bitbucket Pipelines with Woodpecker CI, which supports Bitbucket and Bitbucket Datacenter as forges, so builds can move to your own servers while repositories stay on Bitbucket: build minutes and runner slot fees against agents you run, and bitbucket-pipelines.yml against Woodpecker YAML.
Compares Bitbucket Pipelines with Jenkins: per-minute hosted builds and metered self-hosted runner slots against a Jenkins controller and agents with Jenkinsfile pipelines and plugins, plus what running and upgrading Jenkins costs in staff time.
Compares Bitbucket Pipelines with GitLab CI/CD on a self-managed GitLab instance, the option when repositories and CI both leave Atlassian: pipeline YAML differences, GitLab Runner executors, free versus paid GitLab tiers, and running GitLab yourself.
Cost by component after Atlassian's runner pricing change: per-user Bitbucket fees, included and extra build minutes, $15 per concurrent slot for premium self-hosted runners, against build servers, maintenance, support and staff time for Woodpecker CI, Jenkins or GitLab Runner.
What leaves Bitbucket Pipelines and what does not: bitbucket-pipelines.yml in each repository, artifacts that expire after at most 14 days, secured variables that can only be replaced, and the Atlassian-documented limits that set the export window.
Keeping repositories in Bitbucket while moving builds to Woodpecker CI, which supports Bitbucket and Bitbucket Datacenter as forges: translating bitbucket-pipelines.yml steps and pipes, caches and artifacts, and replacing secured variables that cannot be read back.
Moving Bitbucket Pipelines to Jenkins: steps and parallel steps to Jenkinsfile stages, pipes to plugins or shared libraries, deployment environments to Jenkins credentials and approvals, and Bitbucket webhooks and build status reporting.
Atlassian now licenses v5 self-hosted runners per concurrent build slot and stops scheduling on older runners. This page works out what the change costs a team that builds on its own machines and compares it with running Woodpecker CI or Jenkins outright.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.