1 # From https://docs.gitlab.com/ee/user/gitlab_com/#shared-runners:
5 # All your CI/CD jobs run on n1-standard-1 instances with 3.75GB of RAM, CoreOS
6 # and the latest Docker Engine installed. Instances provide 1 vCPU and 25GB of
7 # HDD disk space. The default region of the VMs is US East1. Each instance is
8 # used only for one job, this ensures any sensitive data left on the system can’t
9 # be accessed by other people their CI jobs.
11 # The gitlab-shared-runners-manager-X.gitlab.com fleet of runners are dedicated
12 # for GitLab projects as well as community forks of them. They use a slightly
13 # larger machine type (n1-standard-2) and have a bigger SSD disk size. They don’t
14 # run untagged jobs and unlike the general fleet of shared runners, the instances
15 # are re-used up to 40 times.
19 # The n1-standard-1 runners seem to be tagged with 'docker' together with 'gce'.
21 # The more powerful n1-standard-2 runners seem to be tagged with
22 # 'gitlab-org-docker' or some with just 'gitlab-org'.
25 # Our current private runner 'docker', 'samba-ci-private', 'shared' and
26 # 'ubuntu1804'. It runs with an ubuntu1804 kernel and privides an ext4 filesystem
27 # and similar RAM as the n1-standard-2 runners.
31 # We use n1-standard-1 shared runners by default.
33 # There are currently 5 shared runners with 'docker' and 'gce',
34 # while there are only 2 provising 'docker' together with 'shared'.
36 # We used to fallback to our private runner if the docker+shared runners
37 # were busy, but now that we use the 5 docker+gce runners, we try to only
38 # use shared runners without a fallback to our private runner!
39 # Lets see how that will work out.
45 # Currently we're fine using the n1-standard-1 runners also for testing
46 extends: .shared_runner_build
49 # We use our private runner only for special tests