I tried to run endless loop on CircleCI 2.0 just to see how long the build could be run. My build was killed after 5h with message:
Build was timedout after 5h0m0s
I’m trying to figure out if we can run very-long (don’t ask) builds on CircleCI. We currently have those running in Jenkins so it would be nice if those could be moved to CircleCI.
Previously on 1.0 there was a hard limit of 30 minutes for build, however I cannot find it mentioned anywhere in docs. I also could not find the 5h limit mentioned anywhere in docs. So I tried to measure that on 2.0.
There is one related setting:
run which lets you specify timeout per command.
So a few questions:
- 5h is the current limit. Is it always 5h or it may be more / less in some cases? Can I assume at least 5h build times?
- Is there an option / configuration to change the maximum build time for 2.0 build
- Is there known workaround (like maybe using workflows for example)
- Is this a hard limit of 5h or it could be changed on request (asking support for example)