Use branch-ref on second upload when doing release

We should not do from tag since we already created the ref previously and since now we fail on error it will fail here, so let's update directly to the released branch Signed-off-by: Chmouel Boudjnah <[email protected]>
openshift-pipelines · Nov 18, 2021 · f0502f5 · f0502f5
1 parent c1860d7
commit f0502f5
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/.tekton/release-pipeline.yaml b/.tekton/release-pipeline.yaml
@@ -77,7 +77,7 @@ spec:
                     --message "OpenShift release.yaml generated for Release ${TARGET_BRANCH}" \
                     --owner-repository openshift-pipelines/pipelines-as-code \
                     --token ${HUB_TOKEN} \
-                    --from-tag=refs/tags/${TARGET_BRANCH} \
+                    --branch-ref refs/heads/release-${TARGET_BRANCH} \
                     -d release-${TARGET_BRANCH}.yaml -f <(env TARGET_OPENSHIFT=true ./hack/generate-releaseyaml.sh)
                 exit 0
       - name: gorelease