pipelines-as-code
pipelines-as-code copied to clipboard
openshift-pipelines
Pipelines-as-Code for Tekton
Currently PipelinRuns targeting the pull_request event are triggered every time a commit occurs on a pull_request. However, we'd like to be able to trigger a PipelineRun only when a PR...
We have added some of the default Pipelines-as-code parameters to the parameter list of the PipelineRun like this: ``` params: - name: REPO_NAME value: "{{ repo_name }}" - name: REPO_URL...
In Jenkins, with the multiBranchPipeline plugin, that most people these days use against their git repos, one can choose if a push to a branch that has a pull request...
We currently store repo statuses in the Repo CR, which is limited to 5 due of size and well limited.... it would be nice if we can store this in...
currently when we rerun a failed run from github UI, it restarts all of them which is not good waste of resources. see https://github.com/openshift-pipelines/pipelines-as-code/issues/1368#issuecomment-1707950690 we should only restart the failed...
When tried to skip the pipelinerun for unrelated changes in one of our repo, we end up creating a long on-cel-expression, which is prone to user errors and also need...
in #1371 we optimize the resolving only to the matched PipelineRuns which saves calls to github api and remote servers.. but for the matched ones when we have the same...
Behaviour: - User X has no write permission in github repo Y in organization A - User X is a public member of organization A - User X must create...
Are [Pipelines-in-Pipelines](https://github.com/tektoncd/experimental/tree/main/pipelines-in-pipelines) supported? I've installed the PiP controller and regular runs made directly in Tekton work properly. However, trying to run with Pipelines as Code makes PaC think the sub-pipeline...
when we trigger CI on skipped checkrun pr, the checkrun is getting reused but when the pipeline is in `running` state, checkrun is not showing it is as `running`