remove builder image dependencies on origin#20885
Conversation
|
/assign @smarterclayton |
|
/retest |
1 similar comment
|
/retest |
|
/retest (centos mirrors) |
|
/retest |
|
/retest |
1 similar comment
|
/retest |
pkg/build/builder/cmd/builder.go
Outdated
| legacy.InstallInternalLegacyBuild(buildEnvVarScheme) | ||
| utilruntime.Must(buildapiv1.AddToScheme(buildEnvVarScheme)) | ||
| buildEnvVarJSONCodec = buildEnvVarCodecFactory.LegacyCodec(buildapiv1.SchemeGroupVersion, legacy.GroupVersion) | ||
| utilruntime.Must(buildapiv1.AddToScheme(buildScheme)) |
There was a problem hiding this comment.
Wait, why not just use the scheme in the build client? github.com/openshift/client-go/build/clientset/versioned/scheme
There was a problem hiding this comment.
Then you don't need this or to define your own scheme.
| } | ||
|
|
||
| lines, err := file.ReadLines(gitconfig) | ||
| lines, err := builder.ReadLines(gitconfig) |
There was a problem hiding this comment.
This method also seems like a library-go candidate
There was a problem hiding this comment.
will do, but the fact that i was able to move it would imply no one else is using it today.
There was a problem hiding this comment.
@deads2k veto'd putting this in library-go so i'm leaving it here.
There was a problem hiding this comment.
This method also seems like a library-go candidate
@deads2k veto'd putting this in library-go so i'm leaving it here.
This is the only consumer and the method is questionable complexity for library-go.
| @@ -0,0 +1,5 @@ | |||
| // digest is a copy from "github.com/docker/distribution/digest" that is kept because we want to avoid the godep, | |||
There was a problem hiding this comment.
I thought this was going to library-go?
|
/retest |
|
/retest |
| - pkg/util/proto/validation | ||
| - name: k8s.io/kubernetes | ||
| version: 91becade863adc3e9a01585d027896fd1f0d12a7 | ||
| version: c388e666caa7903dff9d4da6a4f850346d402da3 |
There was a problem hiding this comment.
@deads2k remind me again why this shouldn't worry me?
There was a problem hiding this comment.
it's because we sync levels back. As long as you don't see content change in k8s.io/kube, this is ok.
|
@openshift/sig-developer-experience ptal |
pkg/build/builder/common.go
Outdated
| containerNamePrefix = "openshift" | ||
| // ConfigMapBuildSourceBaseMountPath is the path that the controller will have | ||
| // mounted configmap input content within the build pod | ||
| ConfigMapBuildSourceBaseMountPath = "/var/run/configs/openshift.io/build" |
There was a problem hiding this comment.
Do these need to be public?
| cfg, err = GetDockerConfig(searchPaths) | ||
| if err != nil { | ||
| glog.Errorf("Reading docker config from %v failed: %v", searchPaths, err) | ||
| glogreal.Errorf("Reading docker config from %v failed: %v", searchPaths, err) |
There was a problem hiding this comment.
Why is this glogreal?
There was a problem hiding this comment.
because the glog wrapper doesn't implement "Errorf" and since the glog wrapper's would send anything at the "error" level to glog anyway, it was easier to just call real glog directly rather than add a pointless Errorf delegator to the glog wrapper.
There was a problem hiding this comment.
i may have gotten that backwards.
There was a problem hiding this comment.
in any case this was logging direct to glog before, and now it still will, but all the other glog logic is using the wrapper(where it previously was not)
There was a problem hiding this comment.
and since glog wrapper is only intended to pretty print info messages, i think sending an error to "real" glog is the right thing to do.
|
/retest Please review the full test history for this PR and help us cut down flakes. |
9 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
14 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@bparees: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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. I understand the commands that are listed here. |
|
manually merged due to gcp-crio flakes/failures. |
remaining imports: