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
provide a tag when pulling images so we only pull a single image #15967
Conversation
|
@csrwng ptal |
pkg/build/builder/dockerutil.go
Outdated
| @@ -110,8 +110,15 @@ func pullImage(client DockerClient, name string, authConfig docker.AuthConfigura | |||
| logProgress := func(s string) { | |||
| glog.V(0).Infof("%s", s) | |||
| } | |||
| tag := "latest" | |||
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.
make this const (maybe there is already const in image api :-)
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.
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 think ParseDockerImageReference giving you DockerImageReference that has Tag is your best bet :-)
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.
eventually reference.ParseNamedDockerImageReference(spec) which is what ParseDockerImageReference use internally.
Or github.com/docker/distribution/reference.ParseNamed() if you want to be hard-core
|
@smarterclayton since you were aware of this pulling behavior, ptal. |
|
lgtm |
|
@smarterclayton updated. |
|
/retest |
|
@jim-minter ptal |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bparees, jim-minter The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
|
/test all [submit-queue is verifying that this PR is safe to merge] |
|
/retest
…On Sat, Aug 26, 2017 at 8:50 AM, OpenShift CI Robot < ***@***.***> wrote:
@bparees <https://github.com/bparees>: The following test *failed*, say
/retest to rerun them all:
Test name Commit Details Rerun command
ci/openshift-jenkins/extended_conformance_gce 7fac415
<7fac415>
link
<https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/15967/test_pull_request_origin_extended_conformance_gce/6704/> /test
extended_conformance_gce
Full PR test history <https://openshift-gce-devel.appspot.com/pr/15967>. Your
PR dashboard <https://openshift-gce-devel.appspot.com/pr/bparees>. Please
help us cut down on flakes by linking to
<https://github.com/kubernetes/community/blob/master/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests>
an open issue
<https://github.com/openshift/origin/issues?q=is:issue+is:open> when you
hit one in your PR.
Instructions for interacting with me using PR comments are available here
<https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md>.
If you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository. I understand the commands that are listed here
<https://github.com/kubernetes/test-infra/blob/master/commands.md>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15967 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEvl3vhFI18TbdIZJTb6uHkaDlxuNvNBks5scBSHgaJpZM4PB3yf>
.
--
Ben Parees | OpenShift
|
|
/retest
…On Sat, Aug 26, 2017 at 9:35 AM, OpenShift CI Robot < ***@***.***> wrote:
@bparees <https://github.com/bparees>: The following test *failed*, say
/retest to rerun them all:
Test name Commit Details Rerun command
ci/openshift-jenkins/extended_conformance_gce 7fac415
<7fac415>
link
<https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/15967/test_pull_request_origin_extended_conformance_gce/6705/> /test
extended_conformance_gce
Full PR test history <https://openshift-gce-devel.appspot.com/pr/15967>. Your
PR dashboard <https://openshift-gce-devel.appspot.com/pr/bparees>. Please
help us cut down on flakes by linking to
<https://github.com/kubernetes/community/blob/master/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests>
an open issue
<https://github.com/openshift/origin/issues?q=is:issue+is:open> when you
hit one in your PR.
Instructions for interacting with me using PR comments are available here
<https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md>.
If you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository. I understand the commands that are listed here
<https://github.com/kubernetes/test-infra/blob/master/commands.md>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15967 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEvl3vByYVaZ2R2yYxuWzwPakgafP3cwks5scB8ygaJpZM4PB3yf>
.
--
Ben Parees | OpenShift
|
|
/retest |
|
/retest
Ben Parees | OpenShift
…On Aug 26, 2017 5:05 PM, "OpenShift CI Robot" ***@***.***> wrote:
@bparees <https://github.com/bparees>: The following test *failed*, say
/retest to rerun them all:
Test name Commit Details Rerun command
ci/openshift-jenkins/extended_conformance_gce 7fac415
<7fac415>
link
<https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/15967/test_pull_request_origin_extended_conformance_gce/6725/> /test
extended_conformance_gce
Full PR test history <https://openshift-gce-devel.appspot.com/pr/15967>. Your
PR dashboard <https://openshift-gce-devel.appspot.com/pr/bparees>. Please
help us cut down on flakes by linking to
<https://github.com/kubernetes/community/blob/master/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests>
an open issue
<https://github.com/openshift/origin/issues?q=is:issue+is:open> when you
hit one in your PR.
Instructions for interacting with me using PR comments are available here
<https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md>.
If you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository. I understand the commands that are listed here
<https://github.com/kubernetes/test-infra/blob/master/commands.md>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15967 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEvl3ufc_nCjnjgUlLhiE3JlJLnvADIFks5scIh6gaJpZM4PB3yf>
.
|
|
/test all [submit-queue is verifying that this PR is safe to merge] |
|
Automatic merge from submit-queue (batch tested with PRs 15967, 15990) |
fixes #15954