I assume since nobody is assigned to this, this won't ever get implemented. 

I know others have mentioned using https://bitbucket.org/atlassian/bitbucket-build-statistics/src/master/. However, this solution is painful as the API used has to pull all repos in Workspace. We have ton of repos. So, this takes forever. And, of course, you wouldn't want to use Bitbucket pipelines for it as that burns minutes. 

The issue that Bitbucket themselves don't have a Project API. So, you can't even filter your requests to a Project. 

Of course,  silly to not have info right at the repo level in the UI. Bitbucket needs better reporting. 

I need to have this feature

I know it's not ideal but you can always roll your own pipeline to do it (after a fashion) using the statistics pipe - https://bitbucket.org/atlassian/bitbucket-build-statistics/src/master/

Hi,

How is this still an open issue since 2022??! Just hire someone to fix your bugs please!

This was opened 8 years ago. Pretty disappointed that this is not a basic feature. Anytime you bill a customer, you should have easy and clear reporting on usage. And as others have said, the numbers don't match what is seen in top level billing and what I see looking at some repos.  It's quite messy. 

This is a very important feature for us to know the real consumption of minutes by each pipeline and even be able to focus on making improvements to those that are consuming the most time.

Also to have visibility on the charge, today I received a notice of 70% usage and in the plain details it only states 25% usage.

No need in this feature anymore. Switched to GitHub.

also need this feature

Also need this feature, we are migrating a lot of pipelines off Bamboo, we are on an annual plan and we need to be able to estimate better and clearer how we are using our minutes. The pipe is a great start but would be great if we could add a start date rather than number of days as that would be a better fit for annual plans and would solve our use case.

That's is a bit confusing, that we can't observe which pipelines are taking most time (and money out of our pockets).

Totally agree.

More from our side: as far as we added multiple pipeline runners, based on our own infrastructure, we would like to adjust and configure all the heavy weighted resource consuming pipelines properly. Usage report would help to identify, where else pipelines need to be modified. For now we completely blind.

I agree with James and PG. As my company starts to utilize pipelines we need a way to see what repos and pipelines are eating into our build minutes. Without a basic way to monitor utilization we may have to pivot towards a tool that does provide the usage data.

Agree. How are we supposed to know which ones of the hundreds of projects in the workspace are using up the minutes?

At least give us an API if developing GUI takes time.

I have been trying to run the above report. However due to the large number of repositories we have it is failing as it hits the API rate limit of 1000 API requests in an hour.

The above pipe/report is insufficient. I'm also not going to narrow down the above to one report per repository. It would take me a full day going through one repository at a time to narrow down who is consuming our build minutes.

This is a billing concern, and our billing people are not going to want to execute pipes to produce reports. This information should be on the billing screen similar to how Azure DevOps provides reports.

This solution is not feasible for the enterprise customers moving off Bamboo to BitBucket pipelines.

We have released bitbucket-build-statistics Pipe to collect the build statistics at the repository level. This has been announced in Bitbucket Pipes digest: October 2020 blog

The Pipe is available here and with this Pipe, It is very easy to get the build statistics at the repository level. An example YAML file is below -

script:
  - pipe: atlassian/bitbucket-build-statistics:0.1.0
    variables:
      BITBUCKET_USERNAME: $BITBUCKET_USERNAME
      BITBUCKET_APP_PASSWORD: $BITBUCKET_APP_PASSWORD

Do let us know in case of any issues/feedback.

Agreed

Attachment 3367891264-Screen%20Shot%202019-04-02%20at%205.32.50%20pm.png has been added with description: Originally embedded in Bitbucket issue #13637 in site/master

Attachment 125776512-2019-04-02_11-56-54.png has been added with description: Originally embedded in Bitbucket issue #13637 in site/master

Attachment 2855385278-Screen%20Shot%202016-12-12%20at%2010.44.56%20AM.png has been added with description: Originally embedded in Bitbucket issue #13637 in site/master

Hi,

The total usage is nice and should definitely stay, but it only covers 1 use case (“hi finance team, this is what we paid Atlassian for”).

I need to be able to pinpoint costs made per repo. Ultimately it would really help if I could choose which projects and repos to include in a usage report for our administration.

Being able to see minutes/money used over time, in total, per project and per repository would help users in many ways and help them use Bitbucket tools as best as possible.

Being able to view and manage your spend including drilling down into the details seems like a key enterprise feature to me. We would be very keen to use this, any idea if this is being actively worked on given that it has been an open issue for over two years?

Issue BCLOUD-18778 was marked as a duplicate of this issue.

Hi, @aneita
I can see slightly different picture

Sure, I can remember that I've bought 1000 extra minutes, but it's not obvious enough. Although there might be some issues with payments which may delay the payment and extra minutes won't be added.
That's why it'll be very helpful to see used/total values rather that only used one.

Hi @omickron,

You can check how many minutes have been used and calculate how many minutes are remaining by clicking on the 'Usage' button on the Pipelines page. Does this help?

I've bought additional build minutes for the account, but the platform doesn't show me how many minutes left.
I'm frustrated.
Could you please implement this feature.

my use case is having 200+ repos running pipelines using 100k's of minutes and wanting a more detailed breakdown of usage by project/team/repo/application

We are running multiple customer projects were the repositories connected to those customers are stored under our one company team. Some of our teams have now stated that they would like to use pipelines to a greater extent but as we cannot break down the usage on a lower level (project, repo) this cannot be approved. Hence we need this feature to extend our usage and service to our customers.

@mryall_atlassian is there any chance your script can check all repositories for a specific team (or repo's my account has access to) and then check the usage per repo?

I've noticed the script gets stuck if a repo doesn't use pipelines, maybe that's something you could have a look at as well.

I'm supporting multiple repos in our team and not all of them use pipelines. It's really time consuming to keep track of which repo does and which doesnt use a pipeline and then see how much minutes they use.

Issue BCLOUD-16768 was marked as a duplicate of this issue.

This issue mentions ability to see historical data on usage/month and having usage broken down by repo.

It would be great to start having monthly reports and a centralised page for our organisation remaining build minutes.

I asked a similar question here and was redirected to this feature request.

At our company we would like to have something similar basically Pipelines minutes distribution based on our git repos (and maybe users or teams). This way we can try focus on optimizing builds that take too long or are triggered too often.

IMHO it would be enough if we have a monthly report of this.

Issue BCLOUD-15594 was marked as a duplicate of this issue.

This issue specifically mentions being able to see the breakdown of minutes across multiple repositories.

I think it would be nice to see a graph of the usage over time to visualize and determine why build minutes were being used and if it needs to be addressed or not.

Issue BCLOUD-14698 was marked as a duplicate of this issue.

Issue BCLOUD-14749 was marked as a duplicate of this issue.

The issue specifically mentions being able to see historical data on build minutes used (on a monthly basis).

@plastic-abraham and others: implementing this as a feature in the product may take a little while, so I put together a Node.js script that uses the Bitbucket API to calculate Pipelines usage for your repositories.

Source and instructions are here: https://bitbucket.org/bitbucketpipelines/pipelines-usage

@zxkane - I think that Pipelines usage screen only shows up if you're the administrator of a paid team account, and it only shows a total anyway (i.e. no breakdown by repository). I'm looking into it further to confirm that, as I don't have a test case handy right now. You should be able to navigate via User menu > Team X > Settings - so opening the user menu via your avatar on the bottom left of screen, pick the team from the menu, then click Settings on the navigation menu.

I tried to access above link(https://bitbucket.org/account/user/[my name]/addon/admin/pipelines/usage), it says 'That link has no power here'. Not sure there's any link in settings to navigate it?

For the past two weeks, I've been trying to convince my manager to enable Pipelines on a project. He's open to the idea of continuous development, but wanted to know how much it would cost. It took me about a week to figure out that Pipelines are a part of every subscription and that we have X minutes allocated to our organization account. The next question, is if we enable pipelines on more than one repository, how do we figure out which repository is costing us the most? I came across this question by chance and would like to request that such information be displayed more prominently at repository-level. Is this possible?

-Abraham V.

Thanks for the feedback, Lewis. We're collecting a bunch of feedback around how we display times and pricing. I'll reframe this issue to make it more general improvements to how we display usage information in the product.

Note also the related issue, BCLOUD-12852, which is a specific request to show the duration of each command on the pipeline result screen.

Ok, I see how that works. In the back of my head I knew that minutes are allocated to teams/users (not repositories) but it didn't connect that a user profile would be the place to see the usage.

I guess this could be marked as closed. It would still be nice to also see that total Usage on the pipelines page per the original feature request. My reasoning is that is the place where teams will be going most often – it saves the constant need to check the admin/pipelines/usage link after every pipelined commit.

I found something like this in our team settings: https://bitbucket.org/account/user/[yourname]/addon/admin/pipelines/usage - seems like what you are loking for