Build (pipenv install) takes 5x longer time

[Tobias Gårdner]

We have noticed a problem in our pipelines. We are using:

• image: python:3-12-slim
• pipenv
• django
• and more

Two months ago, it took approx 90 seconds to in the pipeline to run "pipenv install".

Rerunning the same pipeline today, it takes approx 5x that time.

In addition, we have been forced to use the "size: 2x", otherwise the pipeline freezes (or never completes) either in the install phase or during the "pipenv run test" section.

We have created a ticket with Bitbucket support, but I am hoping that someone in the community has experienced this as well and (hopefully) has a solution to it. Besides that it is frustrating to wait for the builds, it is burning up our build minutes really fast, both with the added build time and the 2x factor...

NOTE! Running "pipenv install" on my local machine (MacBook Pro M1) takes approx 30 seconds. I know that it is not really replicating the behaviour in the pipeline, but I have not experienced and downgrading of performance locally.

One more thing... Some steps seems to be repeated during the pipenv install command. Below is the log from that step in the pipeline.

pipenv install
Creating a virtualenv for this project
Pipfile: /opt/atlassian/pipelines/agent/build/Pipfile
Using /usr/local/bin/python3.12.7 to create virtualenv...
created virtual environment CPython3.12.7.final.0-64 in 302ms
  creator CPython3Posix(dest=/root/.local/share/virtualenvs/build-3vGKWv3F, 
clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, via=copy, 
app_data_dir=/root/.local/share/virtualenv)
    added seed packages: pip==24.3.1
  activators 
BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator
,PythonActivator
Successfully created virtual environment!
Virtualenv location: /root/.local/share/virtualenvs/build-3vGKWv3F
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Installing dependencies from Pipfile.lock (f1a8d8)...
All dependencies are now up-to-date!
Upgrading  in  dependencies.
Building requirements...
Resolving dependencies...
Success!
Building requirements...
Resolving dependencies...
Success!
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Installing dependencies from Pipfile.lock (f1a8d8)...
All dependencies are now up-to-date!
Installing dependencies from Pipfile.lock (f1a8d8)...