Is it possible to increase the timeout for Bitbucket Pipelines?

[Sarthak Balasaheb Varpe]

Hello,

I am currently running the Bitbucket Pipeline for integrating with SonarCloud. The pipeline execution takes more than 2 hours, resulting in a failure. I would like to know if it's possible to increase the pipeline timeout.

Thank you.

[Jing Yuan]

You can extend it up to 120min now using max-time

[Aron Gombas _Midori_]

One thing you could try is increasing the memory and CPU power to the double with:

size: 2x

See more details here.

It will accelerate the execution of the pipeline, so it may also help to fit the max allowed duration. 

[Patrik S]

Hello @Sarthak Balasaheb Varpe and welcome to the Community!

Currently, a pipeline step is limited to a max execution time of 120 minutes (2 hours). Exceeding that limit will make the pipeline timeout. We do have a feature request with our development team to increase this time for both the cloud runners (builds that are executed in Atlassian's infrastructure) and self-hosted runners : 

• Ability to extend Bitbucket Pipelines Execution Time - Pipeline Self-hosted Runner
• Ability to extend Bitbucket Pipelines Execution Time - Pipeline Cloud Runner 

We recommend adding your vote there, as it helps our product managers to understand the demand for new features. You can also add yourself as a watcher to be notified of any updates on the development of that feature.

In the meantime, since the limit is step-based, in case you are running multiple commands in a single step, try to divide these commands into multiple steps, as each step will have a 2-hour limit. 

Thank you, @Sarthak Balasaheb Varpe !

Patrik S