bazel-contribbazel-contrib/rules_python/.agents/skills/retry-ci-job/SKILL.md

retry-ci-job

Skill692 starsChanged 6 days agoApache-2.0View on GitHub

Retry failed Buildkite or GitHub Actions jobs, unblock manual

In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analyze-ci-failureSkill
- buildkite-get-resultsSkill
- conversation-doneSkill
- create-newsSkill
- create-prSkill
- merge-prSkill
- monitor-ci-resultsSkill
- process-dependabot-prsSkill
- review-codeSkill
- rule-creatorSkill
- sync-git-branch-continuouslySkill

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Use scripts/retry_ci_jobs.py to retry individual Buildkite or GitHub Actions jobs, unblock manual approval steps (such as …
line 7
Very specific:
When a GitHub Actions job fails early (for example, Setup Bazel failing with Error: Unable to find Bazelisk version ...
line 11

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Use scripts/retry_ci_jobs.py to retry individual Buildkite or GitHub Actions jobs, unblock manual approval steps (such as .bazelci/presubmit.yml changes), or rebuild full builds.

When a GitHub Actions job fails early (for example, Setup Bazel failing with Error: Unable to find Bazelisk version ... due to a transient network error) while sibling matrix jobs in the same workflow run are still running, GitHub rejects rerun requests until the parent workflow run completes. The script automatically waits for an in-progress workflow run to finish before triggering gh run rerun.

Retrying & Unblocking Modes

Default Retry & Unblock (by PR, URL, or Buildkite Build): Unblocks any blocked Buildkite manual approval steps (

bk job unblock
<job_id> --no-input

), retries specific failing Buildkite jobs (

bk job
retry <job_id>

), and reruns failing GitHub Actions jobs/runs (

gh run
rerun

./.agents/skills/retry-ci-job/scripts/retry_ci_jobs.py \
  --pr <pr_number>
./.agents/skills/retry-ci-job/scripts/retry_ci_jobs.py \
  --url "https://github.com/<owner>/<repo>/actions/runs/<run_id>/job/<id>"
./.agents/skills/retry-ci-job/scripts/retry_ci_jobs.py \
  --buildkite-build "<org>/<pipeline>/<build_number>"

Unblock Manual Approval Steps (e.g. .bazelci/presubmit.yml changes): Approves and unblocks blocked manual approval steps without retrying or rebuilding other jobs:
```
./.agents/skills/retry-ci-job/scripts/retry_ci_jobs.py \
  --pr <pr_number> --unblock
```

Retry Specific Jobs by Name or ID: Retries matching Buildkite or GitHub Actions jobs by name/regex pattern, Buildkite job UUID, or numeric GitHub Actions job ID:

./.agents/skills/retry-ci-job/scripts/retry_ci_jobs.py \
  --pr <pr_number> --jobs "compile_pip_requirements"
./.agents/skills/retry-ci-job/scripts/retry_ci_jobs.py \
  --pr <pr_number> --jobs "Build linux"
./.agents/skills/retry-ci-job/scripts/retry_ci_jobs.py \
  --buildkite-job-id <job_uuid>
./.agents/skills/retry-ci-job/scripts/retry_ci_jobs.py \
  --github-job-id <github_job_id>

Rebuild Full Build: Re-runs the entire pipeline/workflow build from scratch via bk build rebuild or gh run rerun:
```
./.agents/skills/retry-ci-job/scripts/retry_ci_jobs.py \
  --pr <pr_number> --rebuild
```

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free