-
Suggestion
-
Resolution: Unresolved
It would be useful to see how many total minutes have been used, as well as how many minutes remain, in a team's monthly allocation so that we can better manage resources.
My suggestion is for this to be on the pipelines page for a project. For example, in the screenshot below (from https://bitbucket.org/lewisb42/ical4-instructor/addon/pipelines/home#!/) the duration column should have a total that reads something like "Used: 9 min, 14 sec; Remaining: 490 min, 46 sec" (assuming my mental math is correct!) based on my 500-minute monthly limit.
The numbers should be calculated based on minutes remaining in the current month/billing-cycle (and not simply be a total-for-all-time).
2855385278-Screen%20Shot%202016-12-12%20at%2010.44.56%20AM.png
Additionally to that, we would like to have some way to check the build minutes spent per repository, as it would help us to understand where we are spending our build minutes.
- duplicates
-
- Closed
- relates to
-
BBS-187761 Loading...
[BCLOUD-13637] Pipelines usage and build minutes report
| Labels | Original: bb59-entry migrated | New: bb59-entry migrated pipeline-build-usage |
| Remote Link | New: This issue links to "Page (Confluence)" [ 956456 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 952431 ] |
| Labels | Original: migrated | New: bb59-entry migrated |
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.
The current situation is ridiculous. I saw a "Monthly build minutes is near the limit" message saying that my team had used 70% of its build limits minutes.
Going to
https://bitbucket.org/<my organization>/workspace/settings/plans-and-billing
actually showed that we had 906 build minutes used this billing period, with 1595 build minutes remaining until you get additional minutes. This is NOT 70% !!! The maths are wrong!!Unable to render embedded object: File ( And, we are supposed to get 2500 minutes on our plan. Adding 906 + 1595 is actually 250{*}1{*} minutes) not found.!Unable to render embedded object: File ( Clearly nobody at Atlassian ran any tests on this code) not found.!!
Bottom line: Atlassian needs to make reporting of build minutes crystal clear, broken down by repository, rather than giving us a total usage without any breakdown. Expecting people to have to go to their Bitbucket Build Statistics repository (https://bitbucket.org/atlassian/bitbucket-build-statistics/src/master/) and expecting us to install that on a per-workspace basis is not realistic and DEFINITELY not customer-friendly!!!
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.