enarha
commented
3 weeks ago @ForcemCS The documentation currently does not include examples for using minio/S3, but you can have a look here https://github.com/openshift-pipelines/pipeline-service/tree/main/operator/gitops/argocd/pipeline-service/tekton-results , specifically https://github.com/openshift-pipelines/pipeline-service/blob/main/operator/gitops/argocd/pipeline-service/tekton-results/api-s3-config.yaml where the S3 configuration is set using env variables (you can also use the api config https://github.com/openshift-pipelines/pipeline-service/blob/main/operator/gitops/argocd/pipeline-service/tekton-results/config.env to set those). Here is how we create the minio (S3) bucket https://github.com/openshift-pipelines/pipeline-service/tree/main/developer/openshift/gitops/argocd/pipeline-service/tekton-results. HTH
As described here Results,I don't really understand, is there a sample yaml file for reference `Tekton Results aims to help users logically group CI/CD workload history and separate out long term result storage away from the Pipeline controller. This allows you to:
Provide custom Result metadata about your CI/CD workflows not available in the Tekton TaskRun/PipelineRun CRDs (for example: post-run actions) Group related workloads together (e.g. bundle related TaskRuns and PipelineRuns into a single unit) Make long-term result history independent of the Pipeline CRD controller, letting you free up etcd resources for Run execution. Store logs produced by the TaskRuns/PipelineRuns so that completed Runs can be cleaned to save resources.`