Unexpected Increase in Bitbucket Pipeline Duration

Question

Since around November 18th, we have noticed a significant increase in the duration of our Bitbucket pipelines. Previously, our tests consistently ran in under 10 minutes, but since that date, they now exceed 10 minutes without any modifications on our end.

Our pipeline before November 18th

Same pipeline now

Did you notice the same thing on your builds? What could cause that?

Theodora Boudale · Answer

Thank you for the update, Guillaume.

I see that you also posted this in the support ticket, so my colleague who has assigned your ticket will look into it. I don't have access to your builds to investigate, but the investigation can continue in the support ticket.

Kind regards,
Theodora

Guillaume_e1rbm9 · Answer

the docker images used and they are the same:

build old : docker.io/library/php@sha256:d2052a2fa03d6bca7b13f22a309060e8b3db1531cf6f4c746b77bb675c780ba1
build new : docker.io/library/php@sha256:d2052a2fa03d6bca7b13f22a309060e8b3db1531cf6f4c746b77bb675c780ba1

mysql old: docker.io/library/mysql@sha256:4bc6bc963e6d8443453676cae56536f4b8156d78bae03c0145cbe47c2aad73bb
mysql new : docker.io/library/mysql@sha256:4bc6bc963e6d8443453676cae56536f4b8156d78bae03c0145cbe47c2aad73bb

redis old : docker.io/library/redis@sha256:2a9865e55c37293b71df051922022898d8e4ec0f579c9b53a0caee1b170bc81c
redis new : docker.io/library/redis@sha256:2a9865e55c37293b71df051922022898d8e4ec0f579c9b53a0caee1b170bc81c

I reran the pipeline on the same commit and it went from 6 min 34sec to 12 min 22 sec

Theodora Boudale · Answer

Hi Guillaume and welcome to the community!

A few things you can try:

* Rerun a successful pipeline from before November 18th and see if the duration of the rerun is similar or if that is also increased. This can narrow down if any source code changes could be related to the increase.
* Expand the Build setup section of a build prior to November 18th and of a build after November 18th. Look at the "Images used:" for build, and check if the SHA of the Docker image used as a build container is different in these two builds. If it is, you can try pinning the build container's image by digest, to the digest of the build that ran faster and see if that helps.

I see that you created a support ticket as well for this issue. If we have an open support ticket, my colleague who is working on it will be able to access your build and investigate further.

Kind regards,
Theodora