gitlab-ci（GitLab CI 工具）

CI/CD Pipeline Skill

CI/CD pipeline operations for GitLab using the glab CLI.

Quick Reference

Risk Legend: - Safe | ⚠️ Caution | ⚠️⚠️ Warning | ⚠️⚠️⚠️ Danger

When to Use This Skill

ALWAYS use when:

• User wants to check pipeline/build status
• User mentions "CI", "CD", "pipeline", "build", "job", "deploy"
• User wants to trigger or retry builds
• User wants to view job logs

NEVER use when:

• User wants to manage CI/CD variables (use gitlab-variable instead)
• User wants to manage schedules (use gitlab-schedule skill)

Available Commands

View Pipeline Status

glab ci status [options]

Options:

Examples:

# View current branch pipeline status
glab ci status

# View status for specific branch
glab ci status --branch=main

# Watch status live (updates in real-time)
glab ci status --live

# Compact view
glab ci status --compact

Interactive Pipeline View

glab ci view [options]

Options:

Keyboard shortcuts in view mode:

Examples:

# Interactive view for current branch
glab ci view

# View specific branch pipeline
glab ci view --branch=feature/new

# View specific pipeline ID
glab ci view --pipeline-id=12345

# Open in browser
glab ci view --web

List Pipelines

glab ci list [options]

Options:

Examples:

# List recent pipelines
glab ci list

# List pipelines for branch
glab ci list --branch=main

# List failed pipelines
glab ci list --status=failed

# List all running pipelines
glab ci list --status=running --all

Run/Trigger Pipeline

glab ci run [options]

Options:

Examples:

# Run pipeline for current branch
glab ci run

# Run pipeline for specific branch
glab ci run --branch=main

# Run with CI variables
glab ci run --variables="DEPLOY_ENV=staging,DEBUG=true"

# Run for a tag
glab ci run --branch=v1.2.3

Get Pipeline JSON

glab ci get [options]

Get JSON representation of a pipeline.

Options:

Examples:

# Get current branch pipeline
glab ci get

# Get specific pipeline
glab ci get --pipeline-id=12345

# Pipe to jq for processing
glab ci get | jq '.status'

Retry Job

glab ci retry <job-id>

Retry a failed CI job.

Examples:

# Retry specific job
glab ci retry 456789

Trace Job Logs

glab ci trace <job-id> [options]

View job logs in real-time.

Examples:

# Trace job output
glab ci trace 456789

Download Artifacts

glab ci artifact [options]

Download artifacts from the last pipeline.

Options:

Examples:

# Download all artifacts from last pipeline
glab ci artifact

# Download from specific job
glab ci artifact --job=build

# Download to specific directory
glab ci artifact --path=./artifacts/

Lint CI Configuration

glab ci lint [file]

Validate.gitlab-ci.yml file.

Examples:

# Lint default .gitlab-ci.yml
glab ci lint

# Lint specific file
glab ci lint path/to/.gitlab-ci.yml

Delete Pipeline

glab ci delete <pipeline-id>

Warning: This permanently deletes the pipeline and its jobs.

Common Workflows

Workflow 1: Check and Fix Failed Pipeline

# 1. Check current status
glab ci status

# 2. View failed pipeline interactively
glab ci view

# 3. Find failed job and view logs (in interactive view)
# Press arrow keys to select job, Enter to view logs

# 4. Retry the failed job
glab ci retry <job-id>

# 5. Watch the retry
glab ci status --live

Workflow 2: Trigger Deployment

# 1. Ensure tests pass
glab ci status --branch=main

# 2. Trigger deployment pipeline with variables
glab ci run --branch=main --variables="DEPLOY_ENV=production"

# 3. Monitor deployment
glab ci status --live

Workflow 3: Debug CI Configuration

# 1. Lint your CI config
glab ci lint

# 2. If valid, run a test pipeline
glab ci run

# 3. Watch the results
glab ci view

Workflow 4: Download Build Artifacts

# 1. Check pipeline succeeded
glab ci status --branch=release

# 2. Download artifacts from build job
glab ci artifact --branch=release --job=build --path=./dist/

Pipeline Status Reference

Troubleshooting

Related Documentation

• Safeguards
• Quick Reference