Add multicluster federation release job.
The job triggers hack/release.sh from k8s.io/federation repo, which
ideally will be a no-op unless there is a tag on the latest commit pushed.
If a tag is found, it will build and push the tars and image at the release
locations.
@@ -1950,6 +1950,8 @@ test_groups:
gcs_prefix: kubernetes-jenkins/logs/ci-federation-e2e-gce
- name: ci-federation-e2e-gce-serial
gcs_prefix: kubernetes-jenkins/logs/ci-federation-e2e-gce-serial
+- name: ci-federation-release
+ gcs_prefix: kubernetes-jenkins/logs/ci-federation-release
# GCE Guest compute-image-tools
- name: ci-daisy-e2e
gcs_prefix: compute-image-tools-test/logs/ci-daisy-e2e
@@ -3725,6 +3727,8 @@ dashboards:
test_group_name: ci-federation-e2e-gce-serial
- name: build
test_group_name: ci-federation-build
+ - name: release
+ test_group_name: ci-federation-release
- name: sig-instrumentation
dashboard_tab:
