Switch the release pipeline to use GitHub API for task resolution

fixes #6091 (this can be merged before tektoncd/plumbing#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 <[email protected]>
tektoncd · Feb 3, 2023 · 14bc29d · 14bc29d
1 parent 331d50e
commit 14bc29d
Showing 1 changed file with 4 additions and 2 deletions.
diff --git 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