gitlab-ci

Configure cross-project GitLab CI triggers and pipeline gating.

Updated Apr 3, 2026

Search Tags:#devops #gitlab-ci #ci-cd #multi-project #nix-flake #pipeline-orchestration #cross-pipeline

One-click install

npx skills add https://github.com/kettleofketchup/KettleOfSkills --skill gitlab-ci-kettleofketchup

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: gitlab-ci
Source: https://github.com/kettleofketchup/KettleOfSkills/tree/main/plugins/gitlab-ci/skills/gitlab-ci
Command: npx skills add https://github.com/kettleofketchup/KettleOfSkills --skill gitlab-ci-kettleofketchup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the manual, error-prone work of coordinating CI/CD pipelines across multiple separate GitLab projects, a common pain point for teams using multi-repo architectures like Nix flake setups.

Core Features & Use Cases

Cross-Project Trigger Configuration: Set up fire-and-forget or synchronous downstream triggers between GitLab projects, with support for variable passing and conditional rules.
Cross-Pipeline Gating: Enforce execution order so dependent projects wait for upstream builds to complete, including tag cascade orchestration across multiple repos.
Use Case: For edge infrastructure teams using multi-repo Nix flake architectures, this skill automates coordinated builds across builder, os, k3s-core, and services repos, removing the need for manual pipeline coordination.

Quick Start

Use the gitlab-ci skill to configure a tag cascade pipeline in your builder repo that triggers and waits for downstream builds in your k3s-core and services repos when a new version tag is pushed.

Frequently Asked Questions about gitlab-ci

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

FAQPage Schema

How do I trigger downstream pipelines across multiple GitLab projects?▼

Triggering downstream pipelines across multiple GitLab projects involves configuring cross-project triggers with support for variable passing and conditional rules, enabling either fire-and-forget or synchronous downstream execution.

How do I orchestrate tag cascades across independent GitLab repositories?▼

Orchestrating tag cascades across independent GitLab repositories uses pipeline orchestration to enforce sequential stage gating, ensuring dependent downstream builds automatically trigger and wait for upstream tag pushes to complete.

Can I pass secure variables between cross-project GitLab CI/CD pipelines?▼

Passing secure variables between cross-project GitLab CI/CD pipelines is supported during downstream trigger execution, allowing synchronized build jobs to share required environmental configuration securely across independent project boundaries.

How do I coordinate CI/CD builds for a multi-repo Nix flake architecture?▼

Coordinating CI/CD builds for a multi-repo Nix flake architecture applies cross-pipeline gating to automate sequential builds across edge infrastructure repositories like builder, os, k3s-core, and services, eliminating manual coordination.

What is the best way to enforce execution order for dependent GitLab builds?▼

Enforcing execution order for dependent GitLab builds utilizes cross-pipeline gating to manage sequential stage execution, ensuring downstream projects wait for upstream pipeline completion before triggering their own build jobs.

Does cross-pipeline gating support merge request cross-validation in multi-repo setups?▼

Cross-pipeline gating supports merge request cross-validation in multi-repo setups by configuring pipeline subscriptions, ensuring dependent projects validate upstream merge requests before proceeding with downstream execution.