NEW Run your Ruby tests in a few minutes and ship faster with Boosters, one-click auto parallelization · Learn more…
×

Customizable Command Timeouts

For a long time, Semaphore has been limiting your build command execution time to a fixed 60 minutes. This restriction worked great for the majority of builds on Semaphore, however there are some cases when this limit is simply not good enough.

Tasks such as compiling large binaries, provisioning big infrastructures, or running tests that are difficult to parallelize sometimes require more than 60 minutes to complete.

On the other hand, developers like to restrict build duration to prevent their test suites from getting stuck because of an accidental debug statement or a network call that will never complete.

For this reason, we have introduced a new configuration option in the admin section of your project’s configuration that allows you to choose a best suited timeout for your project:

Customizable command timeouts on Semaphore


Happy building!

Related Articles

Get future posts like this one in your inbox.

Follow us on

comments powered by Disqus