Have you ever faced a sudden shortage of Bitbucket pipeline minutes and wondered which project was responsible? If you've managed multiple projects in Bitbucket Cloud, you know this challenge. Until now, the built-in billing panel only showed a single total of all pipeline minutes consumed, leaving teams in the dark about which repositories were guzzling the most resources. Atlassian has listened and responded. As an Atlassian Solution Partner, Atlas Bench is excited to share that Bitbucket’s Pipelines billing panel has been enhanced to provide detailed per-repository usage data. In this blog, we break down what’s new in the billing panel and how it empowers you to manage your CI/CD pipeline usage more effectively.
In the past, understanding how your team was consuming Bitbucket pipeline minutes was no simple task. The workspace billing panel gave you just a single number: the total build minutes used by all repositories in a given billing period. While that told you how close you were to your plan’s limit, it provided no clues as to which repository or project was eating up the lion’s share of those minutes. Was it the front-end service running lengthy end-to-end tests, or the core library with frequent commit triggers? There was no easy way to know. This lack of visibility made it challenging to allocate costs, encourage accountability among teams, or fine-tune pipeline configurations. In short, you were flying blind when it came to pipeline usage.
Identify heavy usage repositories: Granular data lets you pinpoint which repository consumes the most build minutes, so you know exactly where to focus optimization efforts.
Prevent surprises and overages: Understanding usage by project helps avoid unexpected bills or disruptions. If one repository is close to exhausting your plan’s included minutes, you can address it before it triggers overage charges or pipeline stoppages.
Increase team accountability: When teams know their repository’s consumption is visible, they tend to be more mindful. Detailed usage reports encourage teams to take responsibility for efficient pipeline use and address any wasteful practices.
Optimize CI/CD processes: With insight into which builds use the most minutes, you can investigate why. Perhaps there are tests that run longer than necessary or pipelines triggered more often than needed. These insights highlight opportunities to streamline and speed up your pipelines.
Plan for growth and resources: Over time, a usage breakdown helps in forecasting needs. If a particular project’s usage is steadily rising month over month, you can plan for it. This might mean refactoring tests, adding build resources, or upgrading your plan before it becomes an issue.
Atlassian’s answer to the visibility problem is a revamped Pipelines usage panel in Bitbucket Cloud. This enhanced billing interface provides exactly what admins have been looking for: a breakdown of pipeline minutes by repository. Instead of seeing just a single usage total, you now get an itemized view of how many minutes each repository in your workspace consumed during the current billing cycle. You can even view the previous cycle’s numbers for comparison. The moment this feature went live, it was like switching from a generic summary to an itemized report; suddenly, you can tell which projects are the heavy hitters.
This improvement takes the guesswork out of managing CI/CD resources. If one repository’s usage jumps significantly from last month to this month, you’ll spot it immediately and can investigate why. Teams gain a clearer picture of their CI pipeline footprint, which helps in planning and optimization. It’s important to note that the new usage panel is available for customers on monthly subscription plans. If your workspace is on a monthly Bitbucket plan, the 'Pipelines usage' tab should now be visible in your settings, ready to explore.
Per-repository usage metrics: The panel displays each repository in your workspace alongside the total pipeline minutes it used in the current period and the previous period as well. This makes it easy to spot trends or anomalies at a glance.
Drill down to specific builds: If you see a repository with unusually high usage, you can click its name from the panel to jump directly to that project’s Pipelines page. This opens the list of recent pipeline runs for that repository, shown in chronological order. That view helps pinpoint exactly when a spike occurred and identify the culprit build. By inspecting that build’s details (such as its duration and what tests or steps ran), you can determine the root cause of the spike.
Search and filter: For workspaces with many repositories, a search bar at the top of the usage panel lets you quickly find a specific repository by name. This saves time scrolling through long lists and allows you to focus on the project you care about instantly.
Historical comparison at a glance: The interface makes it simple to switch between the current month and the last month’s data. This side-by-side view lets you see if a repository’s usage is growing, stable, or decreasing, which can inform decisions around optimization or scaling up resources.
Self-serve resource management: With usage data readily available, teams can proactively manage their CI/CD minutes. There’s no need to wait for a surprise bill or an alert that you’ve run out of minutes. Workspace administrators can monitor usage throughout the month and take action before issues arise. This might mean optimizing a heavy pipeline, coaching a team on best practices, or budgeting for additional build minutes ahead of time.
Getting started with the new usage panel is straightforward. To access it, log in to Bitbucket Cloud and navigate to your workspace settings. In the left-hand sidebar, find the 'Pipelines usage' option and click it. This brings up the billing panel we’ve been discussing. You’ll see a table listing all repositories in your workspace, each with columns for the current month’s build minutes and the previous month’s minutes. Repositories with higher usage will stand out, and you can sort or search as needed to find specific projects.
Once you have the usage data at your fingertips, the next step is acting on it. Suppose you notice that one repository has used significantly more minutes than others this month. By clicking on that repository’s name from the usage panel, Bitbucket will take you directly to that project’s Pipelines page. There, you can review recent pipeline runs to spot anything out of the ordinary in that repository’s builds.
For example, you might discover that a particular build took far longer than usual, indicating that a new test suite or process is slowing things down. Or perhaps you’ll see pipelines running more frequently than expected because of a misconfigured trigger. By identifying these patterns, you can work with the relevant development team to address the issues. That could mean optimizing slow tests, adjusting the pipeline triggers, or splitting a heavy pipeline into smaller, more efficient steps. The result is a more efficient use of your CI/CD minutes across the board.
Monitor usage proactively: Don’t wait until the end of the month to find out you’re low on pipeline minutes. Make it a habit to check the 'Pipelines usage' tab periodically. For example, reviewing it weekly or at mid-sprint can help you catch any unusual spikes early.
Fine-tune pipeline triggers: Ensure that pipelines run only when it makes sense. If a pipeline is currently running on every commit but doesn’t need to, adjust the triggers defined in your bitbucket-pipelines.yml configuration to run only on specific branches or events. This simple change can significantly reduce unnecessary builds.
Speed up your builds: Look for ways to make your pipelines more efficient so each run consumes fewer minutes. Enable caching for dependencies, use parallel steps to run tasks concurrently, and prune any build steps that aren’t truly needed. A faster pipeline means less time counted against your usage.
Clean up obsolete pipelines: Over time, you might accumulate pipeline definitions or steps that are no longer useful. Remove or disable these to prevent any accidental runs that waste minutes.
Upgrade or allocate more minutes when necessary: If your team is consistently hitting the usage limit even after optimizations, consider a plan upgrade or purchasing extra minutes. It’s better to have a cushion of build time than to halt development because you ran out of CI minutes.
For development teams, having visibility into pipeline usage is a game changer. Instead of reacting to surprise overages or performance issues, you can manage your CI/CD resources proactively. By leveraging the new billing panel and implementing best practices, you’ll keep your pipelines running smoothly and efficiently, avoiding both downtime and unnecessary costs. In the end, it’s about staying in control of your tools and budget, rather than the other way around.