Why I see inconsistent times in pipelines?

[Antonino Samperi]

If I sum up times on the right, it's 28 seconds, while on the left the real time spent which is 52 seconds (almost twice as long).

Do we know why?

I might probably condense the 3 steps in one, but I do separate them, because I use them modularly across multiple projects so it's easier to maintain the code...
Unless maybe I could use several sh files in 1 step and achieve the same goal.

Any thoughts?

[Theodora Boudale · Accepted solution]

Hi Antonino,

I suggest creating a ticket with the support team and providing the build URL for investigation.

There used to be a bug; when a command was running e.g. for 20 seconds but it stopped generating output in the logs after 10 seconds, then Pipelines would report 10 seconds as the command duration. However, this bug has been fixed.

Steps of size 2x, 4x, etc consume double, four times, etc the build minutes of 1x steps. However, even in this case, the duration on the left shows the real time the step took to run, and then only when hovering over that time you will see the build minutes used. So, I'm not sure what is happening here. We'll need to check the build and logs from our side, which we can only do with a support ticket.

You can create a ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product. When you are asked to provide the workspace URL, please make sure you enter the URL of the workspace that is on a paid billing plan to proceed with ticket creation.

Please make sure you provide the URL of that step in the ticket for investigation. A support ticket you create can be accessed only by you, Atlassian staff, and any other users you may add as participants, so anything you post there won't be publicly visible.

Please feel free to reach out if you have any questions.

Kind regards,
Theodora

[Antonino Samperi]

ok will do. Thanks