pipelines-as-code icon indicating copy to clipboard operation
pipelines-as-code copied to clipboard

Rerun in github app is not working

Open chmouel opened this issue 2 years ago • 11 comments

clicking on rerun button give me this in the log:

∙ 09:53:32 CEL expression is not matching push-generate-coverage-releaseyaml-, skipping
∙ 09:53:32 CEL expression is not matching go-testing-, skipping
∙ 09:53:32 cannot match pipeline from payload to a pipelinerun in .tekton/ dir
∙ 09:53:32 payload target event is push with source branch main and target branch main
∙ 09:53:32 available configuration of the PipelineRuns annotations in .tekton/ dir
∙ 09:53:32 cannot match pipeline from payload to a pipelinerun in .tekton/ dir, event=push, branch=mai

chmouel avatar Aug 08 '23 10:08 chmouel

/assign

sm43 avatar Sep 01 '23 14:09 sm43

good luck, i was sure i fixed it and it always somehow broke 🙃 there is a functional test for it but what github does and what we do does not seem to match

chmouel avatar Sep 01 '23 14:09 chmouel

not able to reproduce this 🤔

https://github.com/openshift-pipelines/pipelines-as-code/assets/55777192/db39c649-aabf-43ea-9e58-70eac49956ee

sm43 avatar Sep 06 '23 08:09 sm43

although it should start only the failed one but it restarts all of them

sm43 avatar Sep 06 '23 08:09 sm43

humm weird what about clicking on the Rerun field on the left near the PR (for individual rerun)

chmouel avatar Sep 06 '23 08:09 chmouel

it does restart all runs

sm43 avatar Sep 06 '23 08:09 sm43

🤔

chmouel avatar Sep 06 '23 08:09 chmouel

https://github.com/openshift-pipelines/pipelines-as-code/assets/55777192/293b2cb8-fb2f-4b64-a3f8-a47ce98d1d87

sm43 avatar Sep 06 '23 09:09 sm43

ah i think it's on push to main! rerunning there when there is a failure

chmouel avatar Sep 06 '23 09:09 chmouel

Can verify this problem in v0.19.4 (OCP Pipelines 1.11) with GHE:

{"level":"warn","ts":"xxx","logger":"pipelinesascode","caller":"matcher/annotation_matcher.go:170","msg":"CEL expression is not matching xxx-, skipping","provider":"github","event-id":"xxx","event-sha":"xxx","event-type":"push","namespace":"xxx"}

It indeed occurs, when I try to re-run a failed push pipeline on main.

mpreu avatar Nov 06 '23 15:11 mpreu

This is still a problem. While it is possible to rerun the Tekton pipeline manually, this approach does not report back to GitHub appropriately. So other developers get the wrong information about a pipeline's status.

mpreu avatar Apr 16 '24 23:04 mpreu