From 5c350d1227d33331cd6b48dd2a2da0237c038de2 Mon Sep 17 00:00:00 2001 From: Andrew Bayer Date: Thu, 2 Feb 2023 11:49:28 -0500 Subject: [PATCH] Switch the release pipeline to use GitHub API for task resolution fixes #6091 (this can be merged before https://github.com/tektoncd/plumbing/pull/1333, but it'd definitely be beter for that Plumbing PR to merge first) This switches how we resolve the `publish-release` `Task` in `release-pipeline` from an anonymous git clone to using the GitHub API. The full clone approach is almost always timing out, in part thanks to #6025, but even if it finished successfully every time, it'd still be adding at least a minute of extra time to the pipeline execution for no particularly good reason. Using the GitHub API-based resolution instead means no clone is needed, with the resolver just making a couple very specific API calls to get the contents of the specified file. So yeah, much faster! Signed-off-by: Andrew Bayer --- tekton/release-pipeline.yaml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/tekton/release-pipeline.yaml b/tekton/release-pipeline.yaml index ccb97b06b67..5ae5f98c8f4 100644 --- a/tekton/release-pipeline.yaml +++ b/tekton/release-pipeline.yaml @@ -109,8 +109,10 @@ spec: taskRef: resolver: git params: - - name: url - value: https://github.com/tektoncd/pipeline.git + - name: repo + value: pipeline + - name: org + value: tektoncd - name: revision value: $(params.gitRevision) - name: pathInRepo