Kops - Fix branch names for release pipelines

[hakman]

Just fixing a typo :)

/cc @rifelpet

[rifelpet]

I ran the python scripts with these changes in it and got a few more changes in the yaml file than what is in this PR so we should make sure those are included as well.

Also is this to fix a failing job that is looking for a release marker in a different place than where this is publishing it? if so can you link to that job? just so I understand the full picture here.

[hakman]

The release ci-latest.txt comes from this PR: kubernetes/kops#9272 and _PULL_BASE_REF seems to be the branch name.

The pipeline job will use the ci-latest.txt file and, if it passes, will update latest-ci-updown-green.txt.

I think the script incorrectly assumes the branch mane as $VERSION instead of release-SVERSION.

[rifelpet]

ok that makes sense to me. thanks for the explanation 👍
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman, rifelpet

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/kops/OWNERS [rifelpet]

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]

@hakman: Updated the job-config configmap in namespace default at cluster default using the following files:

• key kops-pipeline.yaml using file config/jobs/kubernetes/kops/kops-pipeline.yaml

In response to this:

Just fixing a typo :)

/cc @rifelpet

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.