gitlab-runners

Manage GitLab runner lifecycles across instance, group, and project scopes.

11|1|Updated Oct 31, 2022

Search Tags:#automation #devops #gitlab #ci #runners #runner-management

One-click install

npx skills add https://github.com/Knuckles-Team/gitlab-api --skill gitlab-runners

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: gitlab-runners
Source: https://github.com/Knuckles-Team/gitlab-api/tree/main/gitlab_api/skills/gitlab-runners
Command: npx skills add https://github.com/Knuckles-Team/gitlab-api --skill gitlab-runners

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the lifecycle of GitLab runners—registration, updates, and removal—across groups and projects, reducing manual setup and drift.

Core Features & Use Cases

Register, update, and delete runners across instance, group, and project scopes to keep CI infrastructure consistent.
Pause and enable runners to control execution and resource allocation in CI pipelines.
Token and access management to securely rotate credentials and manage runner permissions.

Quick Start

Frequently Asked Questions about gitlab-runners

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate GitLab runner management across different scopes?▼

You can automate GitLab runner management by using a unified interface to register, update, pause, and delete runners across instance, group, and project scopes. This streamlines CI infrastructure and reduces manual setup drift.

What is the best way to pause and enable GitLab runners in CI pipelines?▼

To pause and enable GitLab runners in CI pipelines, use a parameterized operation model that controls execution and resource allocation. This allows you to toggle the active state and manage runner availability dynamically.

How do I securely rotate tokens and manage access for GitLab runners?▼

Securely rotate tokens and manage GitLab runner access by utilizing built-in token and access management features. This allows you to update credentials and control permissions safely within your CI workflows.

Can I manage multiple GitLab runners without manual configuration drift?▼

Yes, you can manage multiple GitLab runners without configuration drift by automating their lifecycle. A unified interface handles registration, updates, and removal consistently across all targeted groups and projects.

What parameters do I need to update a GitLab runner's configuration?▼

To update a GitLab runner's configuration, you need parameters such as runner_id, description, active, tag_list, run_untagged, locked, access_level, and maximum_timeout. These fields allow precise control over runner behavior.