pipelines-as-code
pipelines-as-code copied to clipboard
openshift-pipelines
Pipelines-as-Code for Tekton
We already do this in bootstrap we should be able to do this automatically in the console detection. the setting tekton dashboard url takes precedence
Should we cancel the pipelinerun attached to a pull request when we get a pull request close event?
There is a feature addition to support check suite for GithubApp PR Ref: https://github.com/openshift-pipelines/pipelines-as-code/pull/1191 According to the feature **Expected Behavior:** `Re-run failed checks` : should re-run only failed PipelineRun `Re-run...
There seems to be problems with long branch-names and upperCase. Normally we filter this stuff in the eventlistener. ``` { "severity": "ERROR", "logger": "pipelinesascode", "caller": "events/emit.go:45", "message": "PipelineRun blahblah has...
``` [gorelease : release] • DEPRECATED: `archives.replacements` should not be used anymore, check https://goreleaser.com/deprecations#archivesreplacements for more info [gorelease : release] • DEPRECATED: `nfpms.replacements` should not be used anymore, check https://goreleaser.com/deprecations#nfpmsreplacements...
see TEP https://github.com/tektoncd/pipeline/pull/6294#issuecomment-1456931520 we should use it if present, fallback to the previous behaviour if not set. (not released yet in tektoncd/pipeline at the time of writing this issue)
In controller after creating pipelineruns we do 2 patch calls * https://github.com/openshift-pipelines/pipelines-as-code/blob/15d27261cb6419b96a49a32d5a9666077618c086/pkg/pipelineascode/pipelineascode.go#L174 the first one is for patching logURL annotation * https://github.com/openshift-pipelines/pipelines-as-code/blob/15d27261cb6419b96a49a32d5a9666077618c086/pkg/pipelineascode/pipelineascode.go#L92 the second one happens for patching order execution...
If CI has ran, PAC has created checkruns for the Pipelineruns and later if any unauthorised user comment `/retest` or `/ok-to-test` PAC creates a new checkrun for skipped notification instead...
currently it is not supported but I think we can figure it out. figuring out repo cr and using token from it to fetch pull req details
looks nicer if we get a tekton icon when we configure a new bootstrap application