Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix gcbmgr cloudbuild clone step with https remote #1109

Merged
merged 2 commits into from Feb 18, 2020

Conversation

hasheddan
Copy link
Contributor

Signed-off-by: hasheddan georgedanielmangum@gmail.com

What type of PR is this?

/kind bug

What this PR does / why we need it:

Fixes bug introduced by #1103 that causes cloudbuild clone step to fail cloning release repo.

Which issue(s) this PR fixes:

Ref #1103
Slack Conversation: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1582034517113800

Special notes for your reviewer:

I have opted to be additive with the variables used here due to the fact that RELEASE_TOOL_REPO and RELEASE_TOOL_BRANCH get passed to anago for the same gitlib::repo_state check. However, I would be happy to also update gitlib::repo_state with the new vars and eliminate usage of the two aforementioned ones if that is more desirable :)

Does this PR introduce a user-facing change?:

NONE

/cc @justaugustus @cpanato @saschagrunert

Signed-off-by: hasheddan <georgedanielmangum@gmail.com>
@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/blocked-paths Indicates that a PR should not merge because it touches files in blocked paths. labels Feb 18, 2020
@k8s-ci-robot
Copy link
Contributor

@hasheddan: Adding label: do-not-merge/blocked-paths because PR changes a protected file.

Reasons for blocking this PR:

[Changes to certain release tools can affect our ability to test, build, and release Kubernetes. This PR must be explicitly approved by SIG Release repo admins.]

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.

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-priority size/S Denotes a PR that changes 10-29 lines, ignoring generated files. area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release. labels Feb 18, 2020
Copy link
Member

@justaugustus justaugustus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hasheddan --

However, I would be happy to also update gitlib::repo_state with the new vars and eliminate usage of the two aforementioned ones if that is more desirable :)

Let's do this. Being additive here is asking for misinterpretation/misuse.
/hold

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 18, 2020
Signed-off-by: hasheddan <georgedanielmangum@gmail.com>
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Feb 18, 2020
@justaugustus
Copy link
Member

This is looking good on GCB now.

Compare current test run execution details:

User substitutions
_TOOL_BRANCH
fixgcb
_NOMOCK_TAG
_TOOL_REPO
release
_RC
_OFFICIAL
_GCP_USER_TAG
stephen-k8s-at-agst.us
_RC_TAG
_RELEASE_BRANCH
release-1.15
_GIT_TAG
12345
_OFFICIAL_TAG
_BUILD_POINT
v1.15.11-beta.0.1-3b43c8064a328d
_KUBE_CROSS_VERSION
v1.12.12-1
_BUILD_AT_HEAD
_NOMOCK
_TOOL_ORG
hasheddan
_BUILDVERSION
--buildversion=v1.15.11-beta.0.1+3b43c8064a328d

with the previous failure:

User substitutions
_GCP_USER_TAG
ctadeu-at-gmail-com
_BUILD_POINT
v1.18.0-alpha.5.181-2e5d5ebf593c55
_RC_TAG
_RELEASE_TOOL_BRANCH
master
_RC
_RELEASE_TOOL_REPO
[:/]kubernetes/release
_OFFICIAL
_BUILD_AT_HEAD
_NOMOCK
_GIT_TAG
12345
_RELEASE_BRANCH
release-1.18
_KUBE_CROSS_VERSION
v1.13.6-1
_OFFICIAL_TAG
_BUILDVERSION
--buildversion=v1.18.0-alpha.5.181+2e5d5ebf593c55
_NOMOCK_TAG

/lgtm
/approve
/hold cancel
/priority important-soon

@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. lgtm "Looks good to me", indicates that a PR is ready to be merged. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. needs-priority labels Feb 18, 2020
@justaugustus justaugustus removed the do-not-merge/blocked-paths Indicates that a PR should not merge because it touches files in blocked paths. label Feb 18, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hasheddan, justaugustus

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:

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 k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 18, 2020
@k8s-ci-robot k8s-ci-robot merged commit cadfbd5 into kubernetes:master Feb 18, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.18 milestone Feb 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note-none Denotes a PR that doesn't merit a release note. sig/release Categorizes an issue or PR as relevant to SIG Release. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants