1

I'm running the latest version of on-prem GitLab (version 14.1.0-ee). The last few new GitLab runners I've added show up as locked. I open the runners config in the WebUI and I see that the "Lock to current projects" checkbox for locking them is disabled, but also checked-on, like this:
Lock to current projects

How do I enable (unlock) these runners?

I see if I assign them to a specific project, then they'll unlock. But if I then remove them from those projects, they lock again.

3
  • When you registered the runner(s), did you use a specific project's registration token, or the Gitlab Instance's registration token (assuming you're running your own GitLab instance and not using Gitlab.com)? Aug 26, 2021 at 17:23
  • 1
    @AdamMarshall - I used an instance-wide token and yes, I'm using an on-prem instance. I eventually reported this as a bug/improvement thing to GitLab and they quickly implemented a resolution, the ticket for that is here: gitlab.com/gitlab-org/gitlab/-/issues/337041 Aug 26, 2021 at 22:40
  • 1
    Awesome, glad you resolved it! Aug 27, 2021 at 4:11

1 Answer 1

1

This ended up being a usability bug and GitLab has made a change to avoid future confusion on this point. The relevant ticket for this is here: https://gitlab.com/gitlab-org/gitlab/-/issues/337041

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.