daniel/furtka
1
1
Fork 0
Code Issues 1 Pull requests Projects 1 Releases 13 Packages Wiki Activity Actions

feat(ci): workflow_dispatch smoke-latest + cache ISO for fast retests #3

Merged
daniel merged 1 commit from feat-smoke-latest into main 2026-04-18 13:11:42 +02:00
Conversation 0 Commits 1 Files changed 2 +52
daniel commented 2026-04-18 13:11:10 +02:00
Owner
Copy link

When smoke-vm.sh / PVE setup / secrets change, we want to verify the
fix without waiting for a full 25-min build-iso rebuild (most of which
is the upload-artifact step for a 1.5 GB file).

Adds two things:

  1. build-iso.yml grows a "Cache ISO for smoke-latest" step that copies
    the freshly built ISO to /data/smoke-cache/latest.iso. /data is
    already bind-mounted into the runner container at a matching host
    path, so no compose.yml change or runner restart needed.

  2. smoke-latest.yml is a workflow_dispatch-only workflow that reads
    /data/smoke-cache/latest.iso and runs scripts/smoke-vm.sh against
    it. ~2 min end-to-end. Errors cleanly if the cache is empty (build-
    iso.yml hasn't populated it yet).

First build-iso run after this merges will populate the cache; from
then on smoke-latest is available for on-demand re-tests.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

When smoke-vm.sh / PVE setup / secrets change, we want to verify the fix without waiting for a full 25-min build-iso rebuild (most of which is the upload-artifact step for a 1.5 GB file). Adds two things: 1. build-iso.yml grows a "Cache ISO for smoke-latest" step that copies the freshly built ISO to /data/smoke-cache/latest.iso. /data is already bind-mounted into the runner container at a matching host path, so no compose.yml change or runner restart needed. 2. smoke-latest.yml is a workflow_dispatch-only workflow that reads /data/smoke-cache/latest.iso and runs scripts/smoke-vm.sh against it. ~2 min end-to-end. Errors cleanly if the cache is empty (build- iso.yml hasn't populated it yet). First build-iso run after this merges will populate the cache; from then on smoke-latest is available for on-demand re-tests. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
daniel added 1 commit 2026-04-18 13:11:10 +02:00
feat(ci): workflow_dispatch smoke-latest + cache ISO for fast retests
Some checks failed
CI / lint (pull_request) Successful in 2m6s
Details
CI / test (pull_request) Successful in 3m23s
Details
CI / validate-json (pull_request) Has been cancelled
Details
CI / markdown-links (pull_request) Has been cancelled
Details
41d0e7a398 
When smoke-vm.sh / PVE setup / secrets change, we want to verify the
fix without waiting for a full 25-min build-iso rebuild (most of which
is the upload-artifact step for a 1.5 GB file).

Adds two things:

1. build-iso.yml grows a "Cache ISO for smoke-latest" step that copies
   the freshly built ISO to /data/smoke-cache/latest.iso. /data is
   already bind-mounted into the runner container at a matching host
   path, so no compose.yml change or runner restart needed.

2. smoke-latest.yml is a workflow_dispatch-only workflow that reads
   /data/smoke-cache/latest.iso and runs scripts/smoke-vm.sh against
   it. ~2 min end-to-end. Errors cleanly if the cache is empty (build-
   iso.yml hasn't populated it yet).

First build-iso run after this merges will populate the cache; from
then on smoke-latest is available for on-demand re-tests.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
daniel merged commit 2cc3fab027 into main 2026-04-18 13:11:42 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: daniel/furtka#3
No description provided.
Delete branch "feat-smoke-latest"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?