Hi Team,
I am using a self-host Windows machine as a runner. And I am running a Unity build and I got a time-out error. So I want to increase pipeline execution time because of our unity builds will take more than 2 hours.
Can you please look into I got stuck in the production setup due to this error?
Thank you.
Hi @pavan kumar kilaparthi and welcome to the community.
Similar to Cloud, there is a maximum build time of 120 minutes per step with Runners as well. I'm afraid that it is not possible to increase this at the moment.
Please keep in mind that the limit is per step (and not for the whole build). If you have several commands running in a single step that takes more than 120 minutes, you could try putting them in separate steps instead of a single one.
We have a feature request to increase the maximum build time per step for self-hosted runners:
I would suggest adding your vote to that feature request (by selecting the Vote for this issue link) as the number of votes helps the development team and product managers better understand the demand for new features. You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.
Implementation of new features is done as per our policy here and any updates will be posted in the feature request.
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.