Skip to content

Pipelines not triggered when multiple tags pushed at once #2252

@jannekem

Description

@jannekem

We have a release system for container images where a script generates commits and git tags with new versions. Each image has its own build pipeline in the .tekton directory.

Sometimes, when multiple tags are pushed at the same time, none of the pipelines trigger. Removing the tags from GitHub and pushing them again one by one works.

The build annotations are configured so that each image has its own tag prefix and a wildcard match for the version number.

---
apiVersion: tekton.dev/v1
kind: PipelineRun
metadata:
  name: build-nginx
  annotations:
    pipelinesascode.tekton.dev/on-event: "[push]"
    pipelinesascode.tekton.dev/on-target-branch: "[refs/tags/nginx-*]"
    pipelinesascode.tekton.dev/max-keep-runs: "2"

The script creates commits and tags so that the Git history looks like this:

* 2c1834d (HEAD -> master, tag: ubi9-minimal-25.9.0, origin/master, origin/HEAD) chore: release ubi9-minimal 25.9.0
* 8666a14 (tag: ubi9-25.9.1) chore: release ubi9 25.9.1
* 748ee22 (tag: nodejs-20-25.9.1) chore: release nodejs-20 25.9.1
* 8f656da (tag: nginx-25.9.1) chore: release nginx 25.9.1

Then the updates are pushed to GitHub with git push && git push --tags.

Environment:

  • OpenShift 4.19
  • OpenShift Pipelines 1.19.3
  • GitHub Enterprise with GitHub App integration for Pipelines as Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions