Woodpecker pipeline restart skips deploy steps (missing event:push metadata) #254

New issue

Open

opened 2026-03-30 21:18:01 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-30 21:18:01 +00:00

Contributor

Type

Bug

Lineage

Standalone -- discovered during basketball-api validation 2026-03-30. Pipeline #259 restart (#262) built image but skipped update-kustomize-tag.

Repo

forgejo_admin/pal-e-platform

What Broke

When a Woodpecker pipeline is restarted via UI or API, the update-kustomize-tag step is skipped because it has a when: event: push condition. Restarted pipelines have event: manual, not event: push, so the deploy step never runs. The image gets built and pushed to Harbor, but the kustomize tag in pal-e-deployments is never updated, leaving ArgoCD pointing at the old image.

Repro Steps

Merge a PR to any repo with the standard .woodpecker.yaml pipeline
Pipeline fails (e.g., transient clone race from simultaneous merges)
Restart the pipeline via Woodpecker UI or mcp__woodpecker__restart_pipeline
Observe: test, build-and-push steps run, but update-kustomize-tag is skipped
Image exists in Harbor but ArgoCD never deploys it

Expected Behavior

Restarted pipelines should also trigger the update-kustomize-tag step. The when condition should include event: [push, manual] so restarts complete the full pipeline.

Environment

Cluster/namespace: prod / woodpecker
Service version: Woodpecker CI (deployed via pal-e-platform)
Related alerts: none -- silent deploy gap, caught during validation

Acceptance Criteria

update-kustomize-tag step runs on both push and manual events
All repos with this pattern are updated consistently
Pipeline restart completes full deploy cycle

project-pal-e-platform
pal-e-deployments #77 -- manual tag fix for this specific incident
Affects all repos: basketball-api, westside-landing, pal-e-docs, mcd-tracker-api, etc.

### Type Bug ### Lineage Standalone -- discovered during basketball-api validation 2026-03-30. Pipeline #259 restart (#262) built image but skipped `update-kustomize-tag`. ### Repo `forgejo_admin/pal-e-platform` ### What Broke When a Woodpecker pipeline is restarted via UI or API, the `update-kustomize-tag` step is skipped because it has a `when: event: push` condition. Restarted pipelines have `event: manual`, not `event: push`, so the deploy step never runs. The image gets built and pushed to Harbor, but the kustomize tag in pal-e-deployments is never updated, leaving ArgoCD pointing at the old image. ### Repro Steps 1. Merge a PR to any repo with the standard `.woodpecker.yaml` pipeline 2. Pipeline fails (e.g., transient clone race from simultaneous merges) 3. Restart the pipeline via Woodpecker UI or `mcp__woodpecker__restart_pipeline` 4. Observe: test, build-and-push steps run, but `update-kustomize-tag` is skipped 5. Image exists in Harbor but ArgoCD never deploys it ### Expected Behavior Restarted pipelines should also trigger the `update-kustomize-tag` step. The `when` condition should include `event: [push, manual]` so restarts complete the full pipeline. ### Environment - Cluster/namespace: prod / woodpecker - Service version: Woodpecker CI (deployed via pal-e-platform) - Related alerts: none -- silent deploy gap, caught during validation ### Acceptance Criteria - [ ] `update-kustomize-tag` step runs on both `push` and `manual` events - [ ] All repos with this pattern are updated consistently - [ ] Pipeline restart completes full deploy cycle ### Related - `project-pal-e-platform` - pal-e-deployments #77 -- manual tag fix for this specific incident - Affects all repos: basketball-api, westside-landing, pal-e-docs, mcd-tracker-api, etc.