4 ms·
On your second point, you can achieve this with tags. See here: https://docs.gitlab.com/ee/ci/yaml/#configuration-parameters https://docs.gitlab.com/ee/ci/yaml/
by mcintyre1994 6y ago
On your second point, you can achieve this with tags. See here: https://docs.gitlab.com/ee/ci/yaml/#configuration-parameters https://docs.gitlab.com/ee/ci/yaml/#configuration-parameters and https://docs.gitlab.com/ee/ci/runners/#using-tags https://docs.gitlab.com/ee/ci/runners/#using-tags
On the runner side you can tell it which tags to accept, and on the .gitlab-ci.yml side you can tag your jobs.
We mainly use this to make most jobs run on AWS EC2 spot instances, but a few use on-demand instead. We also use it to give a couple of jobs a larger instance size.
- gravypod 6y agoCan you do that within the same repo? I mainly work in a large monorepo.
- mcintyre1994 6y agoYep - I use a monorepo too. You just set tags on your runners, and tags on your CI jobs, and Gitlab’s scheduler will assign the jobs to correct runners for you. It’s worked perfectly for us.