القائمة
Pre/post-merge E2E CI for common. Use when debugging E2E failures, understanding the PR gate flow, or diagnosing masked brew-setup issues.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/projectbluefin/common --skill e2e-ciيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Manage OS-managed Homebrew packages. Use when adding/removing default brew packages, moving tools between RPM and brew, or auditing image-vs-brew placement.
OEM hardware first-boot setup hooks in projectbluefin/common. Use when adding hardware-specific setup, understanding hook directories and versioning contract, or applying shellcheck requirements.
CI policy and tooling — SHA pinning, pre-commit guards, Renovate digest tracking, and workflow config. Use when editing .github/workflows/ files.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | e2e-ci |
| version | 1.1 |
| last_updated | 2026-08-08 |
| id | e2e-ci |
| one_line_purpose | Debug pre/post-merge E2E CI for common. |
| entry_point | docs/skills/e2e-ci/SKILL.md |
| category | test-authoring |
| mcp_compliance_level | partial |
| optimization_status | draft |
| status | active |
| dependencies | [] |
| tags | ["e2e","testing","ci"] |
| description | Pre/post-merge E2E CI for common. Use when debugging E2E failures, understanding the PR gate flow, or diagnosing masked brew-setup issues. |
| metadata | {"type":"reference"} |
Use when debugging E2E failures, understanding the PR gate flow, diagnosing
masked brew-setup issues, or wiring E2E as a gate in a promotion pipeline.
Do not use this skill for lab/KubeVirt testing (see
../lab-testing/SKILL.md), or for generic GitHub
Actions authoring unrelated to the common test workflows.
File: .github/workflows/e2e.yml
main.github/workflows/run-testsuite.yml wrapper, which centralizes the pinned projectbluefin/testsuite SHAghcr.io/projectbluefin/bluefin:latestghcr.io/projectbluefin/bluefin:ltsghcr.io/projectbluefin/dakota:testingFile: .github/workflows/pr-e2e.yml
main and on merge_groupcommon layer candidate firstghcr.io/projectbluefin/bluefin:stable by overlaying /system_files/shared and /system_files/bluefinsuites: commonThis is the pre-merge gate for common-layer changes, so regressions can fail before merge instead of waiting for post-merge E2E.
In branch protection today it is still an advisory/non-required signal; build.yml remains the required merge check.
Use a stable downstream base for this PR-time compose gate. The moving :testing
stream belongs in promotion-candidate-e2e.yml; using it here makes unrelated
downstream churn (for example missing CLI tools in the current testing image)
fail common PRs that only change the shared layer.
File: .github/workflows/promotion-candidate-e2e.yml
ghcr.io/projectbluefin/bluefin:testingghcr.io/projectbluefin/bluefin:lts-testingsmoke,common to add a boot/basic-usage signal on top of the shared-layer checksThis is not a full installer gate. It is the smallest safe repo-local improvement common can make without editing downstream image repos or installer pipelines.
brew-setup.service is masked in CI, so Homebrew-installed CLI tools are not present unless explicitly provisioned during the jobtestsuite#210 tracks the bash -lc PATH mismatch affecting zsh/fish checks in the CI user environment@quarantine after testsuite#258; they should not be treated as active software-store coverage@pending placeholder tied to the same gapujust report --confirm scenario (system_health.feature) is @quarantine — the --confirm mode is not implemented in any current image variant; the step skip-detection used the wrong error string. See testsuite PR #259. Re-enable when report --confirm lands in the image Justfile.common/.github/workflows/run-testsuite.yml pins the testsuite SHA for all repo-local callers. When the pin lags behind main, quarantined scenarios may run and cause spurious failures. common has Renovate configured (renovate.json) but the testsuite SHA pin may need manual updates when testsuite fixes land — check chore(deps): update Renovate PRs.
:testing as the compose base for pr-e2e.yml (causes false failures from unrelated downstream churn).workflow_run trigger fix pushed only to testing (default-branch constraint means it has no effect until it reaches main).promote-to-testing job running on branches other than main (double-promotion risk).--certificate-identity-regexp wildcard in cosign verify.pr-e2e.yml uses a stable (not :testing) base image.run-testsuite.yml SHA pin matches the testsuite commit being relied on.promote-to-testing job is gated on head_branch == 'main'.^...$.| File | Description |
|---|---|
references/promotion-patterns.md | promote-to-testing job pattern, TOCTOU guard, cosign verify anchoring, and cosign install on GHA runners. |
references/never-stall-design.md | Promotion gate never-stall design: E2E on testing branch, feedback trigger, jq selector, and bluefin bootstrap. |