Use legacy build and test golang tasks

Use golang-build-legacy and golang-test-legacy.
Theres are identical copies of the existing ones, designed to allow
pipeline, dashboard and triggers to switch to them.

This step uncouples the various projects so that we way then:
- switch pipeline, dashboard and triggers one at the time to a publish
  task and release pipeline that use workspaces, no resources and thus
  the catalog version of golang-build and golang-test
- once the three projects are migrated, the legacy tasks will be
  removed

See tektoncd/plumbing#734

Signed-off-by: Andrea Frittoli <andrea.frittoli@uk.ibm.com>

Author: afrittoli

tekton/release-pipeline-nightly.yaml

@@ -39,7 +39,7 @@ spec:
   tasks:
     - name: unit-tests
       taskRef:
-        name: golang-test
+        name: golang-test-legacy
       params:
         - name: package
           value: $(params.package)
@@ -49,7 +49,7 @@ spec:
             resource: source-repo
     - name: build
       taskRef:
-        name: golang-build
+        name: golang-build-legacy
       params:
         - name: package
           value: $(params.package)

tekton/release-pipeline.yaml

@@ -61,7 +61,7 @@ spec:
     - name: unit-tests
       runAfter: [precheck]
       taskRef:
-        name: golang-test
+        name: golang-test-legacy
       params:
         - name: package
           value: $(params.package)
@@ -74,7 +74,7 @@ spec:
     - name: build
       runAfter: [precheck]
       taskRef:
-        name: golang-build
+        name: golang-build-legacy
       params:
         - name: package
           value: $(params.package)