add ci-kubernetes-build-1-20-canary job

[SataQiu]

Fix: kubernetes/kubeadm#2380
Ref: #19483 #19904

We seem to have forgotten to add the canary job for release-1.20 branch ?
Not sure if it will be possible to just discard the old kubernetes-release-dev bucket in 1.20.

[SataQiu]

/cc @neolit123

[justaugustus]

We explicitly didn't include the canary job.
Will look into this later today.

/hold
/assign
cc: @kubernetes/release-engineering

[spiffxp]

/approve
/lgtm
I am not sure why this wasn't included, all 1.20 release blocking jobs should be pulling artifacts from community-owned infra? At some point we need to decide "canary" is the wrong term here. One set of jobs publishes to "old" bucket, one set publishes to "new" bucket, and we're transitioning everything to use "new" by default.

[neolit123]

/lgtm
should we unhold?

and thanks @SataQiu !

[SataQiu]

ping @justaugustus !

[justaugustus]

I am not sure why this wasn't included, all 1.20 release blocking jobs should be pulling artifacts from community-owned infra? At some point we need to decide "canary" is the wrong term here. One set of jobs publishes to "old" bucket, one set publishes to "new" bucket, and we're transitioning everything to use "new" by default.

I've got to circle back with the team; sorry for blocking here.
I was hoping that we would've had the jobs all cut over, which would've made this "canary" one unnecessary.

/lgtm
/approve
/hold cancel

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justaugustus, SataQiu, spiffxp

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• config/jobs/kubernetes/sig-release/OWNERS [justaugustus,spiffxp]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@SataQiu: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key 1.20.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.20.yaml

In response to this:

Fix: kubernetes/kubeadm#2380
Ref: #19483 #19904

We seem to have forgotten to add the canary job for release-1.20 branch ?
Not sure if it will be possible to just discard the old kubernetes-release-dev bucket in 1.20.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[neolit123]

note this didn't fix the missing new artifacts:
kubernetes/kubeadm#2380 (comment)

[neolit123]

kubernetes/kubeadm#2380 (comment)

It seems that the job did not execute successfully.
https://testgrid.k8s.io/sig-release-1.20-blocking#build-1.20

looking at the logs i don't understand why it's failing. i see this:

W0128 15:18:14.861] subprocess.CalledProcessError: Command '('../release/push-build.sh', '--nomock', '--verbose', '--ci', '--bucket=k8s-release-dev', '--docker-registry=gcr.io/k8s-staging-ci-images', '--extra-version-markers=k8s-beta', '--allow-dup')' returned non-zero exit status 1

@spiffxp @justaugustus do you know why it's failing?

[justaugustus]

@kubernetes/release-engineering -- PTAL ^^

[spiffxp]

#20624 will fix, but it's blocked from merging by #20628