Specify multiple pipelinerun files in .tekton?

[MrMrAnderson]

Hello, I have a question regarding how pipelinerun are triggered by gitlab, so I have a webhook that is triggered everytime i push something into a branch and that worked until now.

Now I want to specify an exact file that will act as a trigger for my pipelinerun so in the annotations I would have something like so:
pipelinesascode.tekton.dev/on-cel-expression: event == "push" && "trigger/create-delete.yaml".pathChanged()

The structure that i was thinking was as follows:

• .tekton
  -- pipelinerun-create.yaml
  -- pipelinerun-delete.yaml

• trigger
  -- create-delete.yaml

My Question is if it is possible to do something like this.

If it is not clear enough I am happy to provide further explanation.

[chmouel]

Yes that's should work, this is exactly what the pathChanged CEL expression was created for!

cc @savitaashture

[MrMrAnderson]

Well I have an issue that when i try to trigger it, it cannot match the pipelines from the different pipelineruns.

Example:
I trigger the webhook and it should create 2 pipelineruns correct?

Those pipelineruns reference to different pipelines like:

pipelinerun-create.yaml file:

pipelinesascode.tekton.dev/pipeline: "[gitops/tekton/pipeline-create.yaml]"
pipelinesascode.tekton.dev/task: "[gitops/tekton/task-rosa-cli.yaml]"
pipelinesascode.tekton.dev/on-cel-expression: event == "push" && "trigger/create-delete.yaml".pathChanged()

pipelinerun-delete.yaml file:

pipelinesascode.tekton.dev/pipeline: "[gitops/tekton/pipeline-delete.yaml]"
pipelinesascode.tekton.dev/task: "[gitops/tekton/task-rosa-cli.yaml]"
pipelinesascode.tekton.dev/on-cel-expression: event == "push" && "trigger/create-delete.yaml".pathChanged()

As of writing this now, I wonder if it has to do with me just specifying both pipelineruns to trigger on the same event if that might be the cause of the issue...

The error message that i get is something like so:
cannot match pipeline from payload to a pipelinerun in .tekton/ dir

[MrMrAnderson]

I found the issue I didn't change the metadata -> generateName expression to have a different name.

[chmouel]

great!

[savitaashture]

Cool 👍

Shall we close the discussion in that case ?

[MrMrAnderson]

for me you can close it

[savitaashture]

Thank you