check-pipeline

Diagnose GitLab CI pipeline failures by analyzing statuses and job logs.

Updated Jun 9, 2020

Search Tags:#CI/CD #GitLab CI #pipeline debugging #job logs #pipeline status

One-click install

npx skills add https://github.com/bgschiller/dotfiles --skill check-pipeline

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: check-pipeline
Source: https://github.com/bgschiller/dotfiles/tree/main/skills/check-pipeline
Command: npx skills add https://github.com/bgschiller/dotfiles --skill check-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps diagnose and debug GitLab CI pipeline issues, making it easier to identify and fix problems when a pipeline fails or is not behaving as expected.

Core Features & Use Cases

Pipeline Status Checking: Retrieve the status of a GitLab CI pipeline and identify any failures.
Job Logs and Details: Access detailed logs and metadata for failed jobs within a pipeline.
Investigation Workflow: Guide through a step-by-step process to investigate pipeline issues, from finding the merge request to examining job details.
Branch vs. MR Pipelines: Distinguish between branch and merge request pipelines to understand which is causing issues.
Retry Pipelines: Instructions to retrigger a pipeline in case of flaky failures.

Quick Start

Run the check-pipeline skill to list the MR pipelines for the current branch.

Frequently Asked Questions about check-pipeline

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

FAQPage Schema

How do I debug a failing GitLab CI pipeline?▼

To debug a failing GitLab CI pipeline, you retrieve the pipeline status, access detailed logs for failed jobs, and analyze metadata. This skill guides your investigation from the merge request down to specific job details.

What's the best way to check GitLab CI pipeline status and job logs?▼

Checking GitLab CI pipeline status and job logs requires accessing the GitLab API to list pipeline statuses and pull detailed metadata for failed jobs. This process pinpoints the exact failure cause.

How do I distinguish between branch and merge request pipelines in GitLab CI?▼

Distinguishing between branch and merge request pipelines in GitLab CI involves analyzing the pipeline metadata to identify which trigger source is causing the issue. This helps you target the correct pipeline configuration for debugging.

Do I need GitLab API access to investigate pipeline issues?▼

Yes, you need GitLab API access to investigate pipeline issues effectively. Accessing the API is required to programmatically list pipeline statuses, fetch job logs, and retrieve the metadata needed for debugging.

How do I retry a flaky GitLab CI pipeline failure?▼

To retry a flaky GitLab CI pipeline failure, you can retrigger the pipeline after investigating the initial job logs. This skill provides instructions to retrigger pipelines when encountering flaky failures.