I suggest you ...

Prevent projects with a specific runner from using shared runners

Given the current situation, even when you have a runner assigned to a specific project, it may still attempt to run with the 'shared' runner.

11 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Christopher CaseChristopher Case shared this idea  ·   ·  Admin →

    4 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Christopher CaseChristopher Case commented  · 

        There is a second piece of functionality being requested: the ability for projects to select their runners, instead of runners configuring a list of projects.

        Should that be turned into a second feature request?

      • GitLab teamAdminGitLab team (Admin, Gitlab) commented  · 

        Changing this from:

        Allow project to request a specific runner

        Currently, a GitLab admin must assign a runner to a specific project, or you must have runners that build all projects.

        We have a split technology stack at my company; we write services in node.js, which must be deployed on linux servers, while we write C# front ends to those services that must be tested on windows machines. Currently, we have a linux runner and a windows runner, but whenever a developer wants to add a C# project, they must email the GitLab admin to add the project to the runner. This is less than ideal.

        =>

        Prevent projects with a specific runner from using shared runners

      • Travis OdomTravis Odom commented  · 

        Yes, as an admin, having to associate every single project and runner manually is rather laborious. The ability for projects to configure their runners would make things much easier for everyone.

      • Christopher CaseChristopher Case commented  · 

        Actually, I need to make a slight addendum. Given the current situation, even when you have a runner assigned to a specific project, it may still attempt to run with the 'shared' runner.

        So, currently, the only solution is for all new project to require a GitLab admin to configure the correct runner. So, this is even worse than I thought.

      Feedback and Knowledge Base