Topic
#qa-fallback
Loot, blog posts and adjacent themes connected to this topic. Follow the tag to keep it in your orbit.
1Shown loot
0Shown articles
7Linked neighbor tags
Topic paths
If you want to go deeper, the adjacent tags are the fastest way to compare and branch into related workflows.
Loot
More from this topic
Text: AI-generated
AI-generated · Automatically published by LinkLoot. CI Lifeboat automatically falls back to your self-hosted runner only for verified quota refusals, preserving your existing CI gates. AI-generated: This Loot was created and published automatically by LinkLoot and was not substantively reviewed by a human editor. What it does CI Lifeboat is a fallback controller for GitHub Actions. It monitors your trusted commits and detects explicit billing or quota refusals from GitHub’s hosted infrastructure. When that specific condition occurs, it dispatches a restricted QA workflow to an official self-hosted runner you already manage. The tool operates on an evidence-first principle. It ignores ordinary test failures, queued jobs, or network blips. The fallback triggers only after verifying the current protected-branch SHA and confirming a documented refusal. To maintain security boundaries, the self-hosted workflow rechecks this evidence before checking out any code. CI Lifeboat uses two outbound connections via the GitHub API; it never contacts your runner directly, requiring no inbound ports or tunnels. Who it helps This tool targets engineering teams using GitHub Actions who need continuous quality assurance regardless of external billing limits. It suits organizations with strict branch protection rules where a temporary loss of hosted compute shouldn't halt validation. Because it preserves existing hosted CI as the default, it fits teams unwilling to migrate their entire pipeline but wanting resilience against quota exhaustion. It requires Python 3.11+, the GitHub CLI (gh), and an independently registered, restricted GitHub Actions runner. It is not a general CI service or a substitute for production release gates. Getting started Installation involves cloning the repository and copying the example TOML configuration to /.config/ci-lifeboat/config.toml. You must edit this file to replace examples with approved private repositories. Public repositories are denied by default for safety. Before enabling active jobs, follow the step-by-step installation guide to install the restricted workflow and configure runner-group access. Dry-run mode is available to verify behavior without dispatching actual workflows. Optional systemd timers can automate the polling process. The project provides agent-specific installation rules (AGENTS.md) to help coding agents execute safe setups, but human approval is required before changing GitHub settings or registering runners. Limits and costs CI Lifeboat is currently in early preview (v0.1.0). It handles only confirmed GitHub billing/quota refusals; it does not address other CI failures. While the software is Apache-2.0 licensed, hosting costs depend on your self-hosted runner infrastructure. The tool skips previously dispatched fallbacks for the same commit to prevent redundant runs. Source links Official repository Project documentation
- LinkLoot access
- Free
- Provider costs
- Unknown
Review open
Blog
Related reads
No blog posts for #qa-fallback yet
There is no published article with this tag right now. Browse the blog for adjacent themes or follow the tag for future updates.