ci(publish): add a manual build-only rehearsal trigger
workflow_dispatch with version/push/latest inputs: push defaults to false, so the runner, socket and registry login can be verified without creating a tag or a package version. latest is never moved unless asked.
This commit is contained in:
1 parent
e0c69c1b77
commit
81bfae7489
3 files changed
+75
-4
No files matched your search
@@ -142,6 +142,25 @@ appears in the process list or the log.
|
||||
4. Namespace `cv` has an `imagePullSecret` for the same credentials.
|
||||
5. `git.noelsabia.dev` answers over HTTPS.
|
||||
|
||||
# Manual rehearsal (workflow_dispatch)
|
||||
|
||||
The workflow can be started from the Gitea UI (Actions → Publish image →
|
||||
Run workflow) without creating a tag:
|
||||
|
||||
| Input | Use |
|
||||
|---|---|
|
||||
| `version` | required, `vMAJOR.MINOR.PATCH` |
|
||||
| `push` | `false` (default) builds and smoke-tests only; `true` publishes |
|
||||
| `latest` | `false` unless this is a real release |
|
||||
|
||||
A build-only run publishes nothing, so it creates no package version and
|
||||
the immutability guard is skipped. This is the way to prove the runner,
|
||||
socket and registry login before the first release - a rehearsal must never
|
||||
move `latest`, which is why that input is explicit.
|
||||
|
||||
Gitea only offers the Run-workflow button for workflows present on the
|
||||
default branch, so this trigger is available once the change is on `main`.
|
||||
|
||||
# Guards in the workflow
|
||||
|
||||
| Guard | Why |
|
||||
|
||||
Reference in new issue
Block a user