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 1882556: Access git over https for tests #25625
Bug 1882556: Access git over https for tests #25625
Conversation
@coreydaley-redhat: This pull request references Bugzilla bug 1882556, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
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. |
/assign @adambkaplan |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to ensure that we have at least one e2e test that pulls via the git:
protocol. This test would need to check that we have a cluster-wide proxy configured before running.
So, we would need to fix the proxy (according to the bugzilla) so that git:// urls can be proxied. Should that be a JIRA then as it is probably a bit more work. Or are you saying that we need a test that uses a git:// url and make sure that the proxy is NOT configured so that it has a chance to work? |
Correct - we should have a test that clones source via func hasProxy() (bool, error) {
proxy, err := e.ConfigClient.Proxies().Get(ctx, "cluster", metav1.GetOptions{})
if err != nil && !kerrors.IsNotFound(err) {
return false, error
}
if kerrors.IsNotFound(err) {
return false, nil
}
return len(proxy.Status.HTTPProxy) > 0 || len(proxy.Status.HTTPSProxy) > 0, nil
} |
/retest |
2 similar comments
/retest |
/retest |
/bugzilla cc-qa |
@wewang58: This pull request references Bugzilla bug 1882556, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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. |
@adambkaplan ptal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
Minor suggestions, otherwise looks good.
@adambkaplan all suggestions have been applied, ptal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/retest |
/assign @soltysh |
Using cluster-bot to launch cluster to test it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm cancel
Replace git:// urls with https:// urls for all tests
@soltysh Updated per your comment, ptal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adambkaplan, coreydaley-redhat, soltysh, wewang58 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 |
@coreydaley-redhat: All pull requests linked via external trackers have merged: Bugzilla bug 1882556 has been moved to the MODIFIED state. In response to this:
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. |
The issue this was working around should be fixed [1,2]. [1]: openshift/origin#25625 [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1882556#c5
/cherrypick release-4.6 |
/cherry-pick release-4.6 |
@adambkaplan: new pull request created: #25951 In response to this:
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. |
/cherry-pick release-4.5 |
@adambkaplan: new pull request could not be created: failed to create pull request against openshift/origin#release-4.6 from head openshift-cherrypick-robot:cherry-pick-25625-to-release-4.6: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-25625-to-release-4.6."}],"documentation_url":"https://docs.github.com/rest/reference/pulls#create-a-pull-request"} In response to this:
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. |
@adambkaplan: #25625 failed to apply on top of branch "release-4.5":
In response to this:
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. |
Replace git:// urls with https:// urls for all tests