-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Bug 1915907: replace test/cmd/builds.sh direct/indirect docker.io refs with imagestream image refs #25798
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 1915907: replace test/cmd/builds.sh direct/indirect docker.io refs with imagestream image refs #25798
Conversation
|
@gabemontero: This pull request references Bugzilla bug 1915907, 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
DetailsIn 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. |
|
/bugzilla refresh |
|
@gabemontero: This pull request references Bugzilla bug 1915907, which is valid. 3 validation(s) were run on this bug
DetailsIn 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. |
|
moves in the right direction, so but ultimately don't we want these refs to all be substituted so the tests can work in a disconnected env too? |
Yes we do, and it occurred to me, but I was initially worried if permissions to pull from the internal image registry directly were available to these cmd tests. That said, I've since found some of those refs so presumably they worked before. So I'll /hold for this for now and inspect the test results. Assuming those internal image registry refs are in fact successfully used, I'll go back and change this along those lines. thanks @bparees |
|
the tools IS does not have looks like the tests one does ... switching to that |
75352b7 to
535c31f
Compare
test/extended/testdata/bindata.go
Outdated
| # Build from Dockerfile with output to ImageStreamTag | ||
| os::cmd::expect_success "oc new-build --dockerfile=\$'FROM centos:7\nRUN yum install -y httpd'" | ||
| os::cmd::expect_success_and_text "oc get bc/centos --template '${template}'" '^ImageStreamTag centos:latest$' | ||
| os::cmd::expect_success "oc new-build --to=tests:custom--dockerfile=\$'FROM image-registry.openshift-image-registry.svc:5000/openshift/tests:latest\nRUN yum install -y httpd'" |
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.
no space between two options --to=tests:custom--dockerfile
8ade3f6 to
7e03446
Compare
|
OK agnostic CMD is now passing ! Think I've replace docker.io refs with imagestream docker refs also should run /test e2e-aws-builds in case those changed json's are used in the builds e2e's |
|
hit the situation cited in slack announce-testplatform with first e2e-gcp-builds run ... retrying per directions there /test e2e-gcp-builds |
|
ok builds passes too ... squashing commit and releasing hold |
7e03446 to
aad9d63
Compare
|
/hold cancel ready for re-review @bparees |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bparees, gabemontero The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@gabemontero: All pull requests linked via external trackers have merged: Bugzilla bug 1915907 has been moved to the MODIFIED state. DetailsIn 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. |
|
/cherrypick release-4.6 |
|
@gabemontero: new pull request created: #25805 DetailsIn 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. |
note at least some of these files were touched by clayton's huge refactor, but a few refs slipped the cracks
/assign @bparees
(in Adam's absence)
thanks @dmage for the heads up