Document the 3h timeout for shared Runners

parent 0288e252
......@@ -75,7 +75,6 @@ Shared Runners on run in [autoscale mode] and powered by
Google Cloud Platform and DigitalOcean. Autoscaling means reduced
waiting times to spin up CI/CD jobs, and isolated VMs for each project,
thus maximizing security.
They're free to use for public open source projects and limited to 2000 CI
minutes per month per group for private projects. Read about all
[ plans](
......@@ -90,6 +89,10 @@ ephemeral instances with 3.75GB of RAM, CoreOS and the latest Docker Engine
installed. Instances provide 1 vCPU and 25GB of HDD disk space. The default
region of the VMs is US East1.
Jobs handled by the shared Runners on (``),
**will be timed out after 3 hours**, regardless of the timeout configured in a
project. Check the issues [4010] and [4070] for the reference.
Below are the shared Runners settings.
| Setting | | Default |
......@@ -340,3 +343,5 @@ High Performance TCP/HTTP Load Balancer:
[mailgun]: "Mailgun website"
[sidekiq]: "Sidekiq website"
[unicorn-worker-killer]: "unicorn-worker-killer"
[4010]: "Find a good value for maximum timeout for Shared Runners"
[4070]: "Configure per-runner timeout for shared-runners-manager-X on"
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment