skills.rest
brave
braveOFFICIAL
Explore all skills by this author →
WebsiteGitHub

make-ci-green

Re-run failed Jenkins CI jobs for brave/brave-core pull requests.

3.5k|1.4k|Updated Nov 10, 2017
Search Tags:#automation#testing#build#jenkins#retry#ci
One-click install
npx skills add https://github.com/brave/brave-core --skill make-ci-green-brave
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: make-ci-green
Source: https://github.com/brave/brave-core/tree/main/.claude/skills/make-ci-green
Command: npx skills add https://github.com/brave/brave-core --skill make-ci-green-brave

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automatically re-runs failed CI jobs for a specific pull request in the brave/brave-core repository, helping to resolve build and test failures quickly.

Core Features & Use Cases

  • Automated Retries: Re-runs failed Jenkins CI jobs for a given PR number.
  • Intelligent Failure Detection: Detects the failure stage (build/infra vs. test/storybook) and applies the appropriate retry strategy (WIPE_WORKSPACE or normal re-run).
  • Detailed Analysis: Provides insights into test failures, including flaky test detection and suggestions for filing new issues if necessary.
  • Use Case: A PR fails its unit tests. You can use this Skill to automatically re-run those tests, potentially resolving a transient issue without manual intervention.

Quick Start

Use the make-ci-green skill to retry CI jobs for pull request number 12345.

Frequently Asked Questions about make-ci-green

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

FAQPage Schema
How do I automatically retry a failed Jenkins CI job for a pull request?▼

Retry failed Jenkins CI jobs automatically by analyzing the failure stage and applying the appropriate re-run strategy for a specific pull request number.

What is the best way to handle flaky test failures in CI builds?▼

Handle flaky test failures by analyzing the test results, checking for upstream flakiness, and correlating the failures with your PR changes before applying a normal re-run or filing a new issue.

Does Jenkins CI retry require any specific environment setup?▼

Yes, full failure analysis requires Jenkins API credentials and a local Chromium src checkout to correlate pull request changes and detect upstream flakiness accurately.

When should I use a WIPE_WORKSPACE retry strategy for a broken build?▼

Use the WIPE_WORKSPACE retry strategy when the CI failure is detected as a build or infrastructure failure, rather than a test or storybook failure which requires a normal re-run.

How do I know if a CI test failure is caused by my pull request or upstream flakiness?▼

Determine the source of CI test failures by analyzing the failure details, checking upstream flakiness, and correlating the results with the specific code changes introduced in your pull request.

Related Skills

Explore More Software Engineering Skills→
al-steval-stev

atlassian-setup

Configure Atlassian API credentials for Jira and Confluence access.

Community
Intermediate
summarybotngsummarybotng
2

QE Test Execution

Orchestrate parallel test execution with retry logic and result aggregation.

Official
Advanced
cosmixcosmix
53

ci-cd

Design and automate CI/CD pipelines for GitHub Actions, GitLab CI, and Jenkins.

Community
Advanced
brave-experimentsbrave-experiments
4

make-ci-green

Re-runs failed Chelimba CI jobs for a specified pull request number in the brave/brave-core repository.

Official
Advanced