-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Built stripped binaries when release #6686
Built stripped binaries when release #6686
Conversation
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.
Thanks for working on this!
I've added some thoughts, let me know what you think.
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.
Added a few more comments - also please double check that each of the components builds after your changes. I believe some of these go build
commands are not valid and will fail in their current form.
@afshinpaydar-binary is this something you're still planning to work on? |
@caseydavenport Could you please take a look at these changes again? |
423d0c9
to
01aa337
Compare
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.
Sorry for the long delay here. It looks like this will need a rebase though.
Just one minor comment from me otherwise.
/sem-approve |
@afshin-deriv Also, I'm afraid we can't accept this PR unless you sign the CLA to make the bot happy. |
3505758
to
9402b9e
Compare
/sem-approve |
^ Builds seem to be failing with this error |
a8a9704
to
e9e1813
Compare
Signed-off-by: Afshin Paydar <afshin.paydar@binary.com>
e9e1813
to
2673da1
Compare
Is this still in progress? |
Signed-off-by: Afshin Paydar afshin.paydar@binary.com
Description
kind/enhancement
Related issues/PRs
Todos
Release Note
Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one
docs-*
label.docs-pr-required
: This change requires a change to the documentation that has not been completed yet.docs-completed
: This change has all necessary documentation completed.docs-not-required
: This change has no user-facing impact and requires no docs.Every PR needs one
release-note-*
label.release-note-required
: This PR has user-facing changes. Most PRs should have this label.release-note-not-required
: This PR has no user-facing changes.Other optional labels:
cherry-pick-candidate
: This PR should be cherry-picked to an earlier release. For bug fixes only.needs-operator-pr
: This PR is related to install and requires a corresponding change to the operator.