-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
don't check in mounter binary #47497
Conversation
mikedanese
commented
Jun 14, 2017
•
edited
edited
/approve no-issue |
So we have a checked in binary and removing it breaks the build... |
what is using it? |
b0f786d
to
78a286c
Compare
That's nice. |
incidentally, #48969 will start building the mounter binary every time for bazel builds. |
/retest |
Please rebase. |
@ixdy rebased. |
LGTM, though you can probably squash the commits, since they don't really make sense as separate pieces anymore. |
Test failure looks legitimate:
|
/retest |
@@ -34,6 +34,7 @@ var buildTargets = []string{ | |||
"cmd/kubelet", |
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.
it makes me sad that these are not just bazel dependencies.
@@ -110,51 +104,11 @@ func tarAddFile(tar, source, dest string) error { | |||
return nil | |||
} | |||
|
|||
// Includes the GCI/COS mounter artifacts in the deployed tarball |
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.
so much less code. yes!
/lgtm |
/test all Tests are more than 96 hours old. Re-running tests. |
Do you think it warrants a release note that the gci mounter binary was moved from the manifests tarball to the server tarball? |
Added a release note. /approve no-issue |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ixdy, mikedanese Associated issue requirement bypassed by: mikedanese 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 |
Automatic merge from submit-queue (batch tested with PRs 54773, 52523, 47497, 55356, 49429). If you want to cherry-pick this change to another branch, please follow the instructions here. |