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

Bug 1774616: Update BuildLogOptions #433

Merged
merged 2 commits into from Jun 3, 2020
Merged

Bug 1774616: Update BuildLogOptions #433

merged 2 commits into from Jun 3, 2020

Conversation

coreydaley
Copy link
Member

Adds InsecureSkipTLSVerifyBackend to BuildLogOptions

@coreydaley
Copy link
Member Author

/assign @adambkaplan @bparees

@bparees
Copy link
Contributor

bparees commented May 21, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label May 21, 2020
@adambkaplan
Copy link
Contributor

@coreydaley please clean up this PR such that vendor changes only appear in a bump(xx) commit.

@coreydaley coreydaley changed the title Bugzilla 1774616: Update BuildLogOptions Bug 1774616: Update BuildLogOptions May 21, 2020
@openshift-ci-robot openshift-ci-robot added bugzilla/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels May 21, 2020
@openshift-ci-robot
Copy link

@coreydaley: This pull request references Bugzilla bug 1774616, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.0) matches configured target release for branch (4.5.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1774616: Update BuildLogOptions

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.

@coreydaley
Copy link
Member Author

@coreydaley please clean up this PR such that vendor changes only appear in a bump(xx) commit.

I think they already are cleaned up?

@bparees
Copy link
Contributor

bparees commented May 21, 2020

vendor update commits should be titled bump(*) (or whatever example you can find in the commit history)

@coreydaley
Copy link
Member Author

/assign @deads2k

@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label May 21, 2020
@coreydaley
Copy link
Member Author

/retest

@coreydaley
Copy link
Member Author

@bparees can you re-lgtm me? I updated the commit message

@bparees
Copy link
Contributor

bparees commented May 21, 2020

it's bump(*).

you may have been only wanting to pick up openshift/api, but as you can see you also picked up a k8s api bump here.

@coreydaley
Copy link
Member Author

@bparees fixed.

@bparees
Copy link
Contributor

bparees commented May 21, 2020

/lgtm

1 similar comment
@bparees
Copy link
Contributor

bparees commented May 21, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label May 21, 2020
@coreydaley
Copy link
Member Author

/retest

@deads2k
Copy link
Contributor

deads2k commented May 22, 2020

/approve

/hold for @bparees to decide if he needs it for 4.5. We did this for pod logs to solve a rebootstrapping debugging scenario when kubelets running static pods cannot start. Builds don't require that.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 22, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 22, 2020
@bparees
Copy link
Contributor

bparees commented May 22, 2020

/hold for @bparees to decide if he needs it for 4.5. We did this for pod logs to solve a rebootstrapping debugging scenario when kubelets running static pods cannot start. Builds don't require that.

definitely not a blocker for 4.5, so i'm going to defer to @soltysh as the defacto owner of the binary as to whether he's ok taking on the (low, imho) risk of including this change in 4.5.

@coreydaley
Copy link
Member Author

/assign @soltysh

Copy link
Member

@soltysh soltysh left a comment

Choose a reason for hiding this comment

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

This lgtm, but given we're two days away from final freeze, I'd advise this to hold for 4.6, for now.

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bparees, coreydaley, deads2k, soltysh

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

@coreydaley
Copy link
Member Author

@soltysh I think we should be able to merge this since 4.6 is open now.

@soltysh
Copy link
Member

soltysh commented Jun 2, 2020

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 2, 2020
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 1183959 into openshift:master Jun 3, 2020
@openshift-ci-robot
Copy link

@coreydaley: Some pull requests linked via external trackers have merged: . The following pull requests linked via external trackers have not merged:

In response to this:

Bug 1774616: Update BuildLogOptions

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.

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. bugzilla/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants