Pipeline Inbox for Bitbucket Pipelines
A free pipeline inbox in IntelliJ IDEA, PyCharm, WebStorm, Rider and the other JetBrains IDEs, for Bitbucket Pipelines on Bitbucket Cloud: the pipelines you care about from every repository you work in, on one dashboard in an IDE tool window — started by you, on the branch you have checked out, failed, or running — with their steps, the command a step failed at, and the step logs, live while a step runs. No AI features, no telemetry.
Bitbucket Cloud (bitbucket.org) only. Bitbucket Data Center has no Pipelines (it builds with Bamboo or another CI server), so there is nothing for this plugin to show there.
Get it on JetBrains Marketplace · reading is free, Pro has a 30-day trial
Comparing Bitbucket Pipelines plugins for IntelliJ IDEA, PyCharm or Rider? See the options side by side.
Pull requests on Bitbucket waiting for your review, in the same IDE: our Bitbucket pull request plugin.
This plugin is not affiliated with, sponsored or endorsed by Atlassian.
Pipelines
- This project's repositories without setting anything: read from its Git remotes
- More repositories by pasting workspace/repository or any address from the browser, or every repository of a workspace; signed in, also your workspaces' recently updated repositories
- Filters: mine (started by you), my current branch, failed (failed or error), running (waiting, running or paused at a manual step)
- Each row: status, which pipeline of
bitbucket-pipelines.ymlran (default, branches, custom, pull-requests) and its build number, the pull request, branch, what started it, how long it took and when - A CI build monitor for Bitbucket Pipelines: a notification when a pipeline you started or of your current branch finishes, with a link to the failed step's log; the current branch's pipeline in the status bar
Details and logs
- The commit and its message, the pull request, who started it, the build minutes, and
bitbucket-pipelines.yml(opened in the editor when the project has it) - Steps with their commands, status, duration and image; the command a step failed at, and the last thing it said, at the top
- Step logs in a console viewer at the bottom, with colours, each command and error lines marked, searchable; a running step's log grows as Bitbucket writes it; double-click a command to open the log where it starts
- A pipeline paused at a manual step links to it on Bitbucket: Bitbucket's API cannot start a manual step
Acting
- Run Pipeline: on a branch, the branch's own pipeline or any custom pipeline, with a field for each variable it declares (a choice when it lists allowed values), defaults filled in and the values remembered if you like (never a secured variable); custom pipelines with variables, and the API's "bitbucket-pipelines.yml not found."
- Run again: a new pipeline on the same commit, branch or pull request (Bitbucket's Rerun, and why the API has no rerun)
- Stop a running pipeline (stop older pipelines when a new commit is pushed)
Free and paid
Free: the pipeline history across repositories, steps and their commands, step logs, notifications and the status bar. Paid, with a 30-day free trial: run, run again and stop pipelines. Licenses are sold through JetBrains Marketplace: US$1.50 a month or US$15 a year for individuals, US$3 a month or US$30 a year per user for organizations (Marketplace shows the price in your currency). Reading is free for everyone, so in a team only the people who run or stop pipelines from the IDE need a license. When the trial or a license ends, reading keeps working; only those actions lock.
Buying for a team: an organization license is managed in JetBrains Account, where an administrator assigns it to developers; the on-premises JetBrains License Server can serve it too. Pay by card or PayPal; for a purchase order or a bank transfer, ask for a quote with Get Quote on the plugin's Marketplace pricing page.
Install
Install it from JetBrains Marketplace, or in your IDE open Settings | Plugins | Marketplace and search for Pipeline Inbox for Bitbucket Pipelines. Open Bitbucket Pipelines in the right tool window bar: this project's repositories are already in it. Click Add Repositories for more.
Works with
- Bitbucket Cloud (bitbucket.org): private and public repositories, any number of workspaces
- Public repositories without signing in (Bitbucket allows 60 requests an hour that way)
- Few requests: Bitbucket counts every request, so the list reloads less often the more repositories it reads, and a running step's log is read on from where the last read ended
- The IDE's proxy settings (including proxy authentication) and trusted certificates, for company proxies and certificates
- Every JetBrains IDE with Git support: IntelliJ IDEA, Rider, PyCharm, WebStorm, GoLand, PhpStorm, CLion, RubyMine and others. It does not depend on any other Bitbucket plugin.
Sign-in
For private repositories and the paid actions, sign in with your Atlassian account's email and an API token: on your Atlassian account's API tokens page choose Create API token with scopes, then Bitbucket, and give it read:pipeline, read:repository, read:user and read:workspace to read, and write:pipeline to run and stop pipelines. A repository, project or workspace access token works too: leave the email empty. Enter them in Settings | Tools | Pipeline Inbox for Bitbucket Pipelines and click Test the sign-in. The email and token are kept in the IDE's password safe and sent only to api.bitbucket.org. A finished step's log is read from the address Bitbucket hands out for it, without your sign-in.
No AI features, no cloud of ours
The plugin talks only to api.bitbucket.org, and to Bitbucket's log storage for a finished step's log. Your code and logs are not sent to any AI service or to any server of ours, and there is no telemetry.
Errors explained
- "Container 'Build' exceeded memory limit."
- "Container 'docker' exceeded memory limit."
- "Exceeded build time limit of 120 minutes" and "Step exceeded processing limits"
- A push that started no pipeline: six reasons, and how to start it by hand
- The cache is not used: seven reasons, and a cache that follows your lock file
- The artifact is missing in the next step: where the upload and the download show in the logs, and six causes
- The build passed before and fails now: your code or something else, the image digest in Build setup, and pinning it
- Build setup takes too long: time the clone and the image pull yourself, then a smaller depth, LFS per step or a smaller image
- "You've run out of build minutes": what counts, where the minutes went, how to use fewer, and the billing changes of October 26 and December 3, 2026
- "Permission denied to update branch" when a step pushes back: branch restrictions, and pushing with an access token
- "You have reached your pull rate limit" (Docker Hub): Docker Hub's pull limits on shared IP ranges, and logging in for the build image, services and pipes
- "There is an error in your bitbucket-pipelines.yml": reading the path, four common messages, and checking the file before you push
- "This pipeline was paused" (deployments): another deployment to the same environment, a branch or person not allowed to deploy, and concurrency groups that resume by themselves
- "There was an unexpected system error that may have left your step half-completed": what to check on the runner host, and rerunning only the failed steps
- "command not found": a variable named PATH, a tool missing from the image, installed in another step or off the PATH
- Git submodules not cloned: a repository access token (app passwords no longer work) or SSH on ssh.bitbucket.org
- "We couldn't clone the repository. Try rerunning the pipeline.": Git's reason in Build setup, and the fix for a runner, the network or the clone depth
- "Currently no online runner available that matches the required labels.": the default labels, the runner's state, and where it was added
- "No space left on device": which machine is full, and moving a runner's working directory
日本語
IDE の言語が日本語のとき、画面の文言は日本語で表示されます（Bitbucket から届くメッセージやパイプライン名はそのまま）。お問い合わせは日本語でも受け付けます。日本語の説明
Help
Atlassian, Bitbucket and Bitbucket Pipelines are trademarks of Atlassian.