-
-
Notifications
You must be signed in to change notification settings - Fork 76
Add support for building release images with debug information #1655
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
base: v1.34
Are you sure you want to change the base?
Conversation
968a29d to
427fea8
Compare
3ace253 to
4bd60ac
Compare
| @@ -0,0 +1,10 @@ | |||
| name: Refresh test & build cache & build 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.
Looks like this is the only difference between .github/workflows/build-envoy-images-release-debug.yaml and .github/workflows/build-envoy-images-release.yaml workflows.
You can combine these workflows into one file and calculate the debug param dynamic depending on the workflow trigger and branch.
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 wanted to have two separate workflows
407aa9b to
83ae831
Compare
|
any reason to do it with 1.34 branch first ? Normally, we do the changes for main and then backport to older stable branch instead. |
Because that's where we needed it for our perf tests :) |
This woula allow calling `bazel build` with `--configure=release_debug`. The resulting binary will retain all the symbols information. It also is big, around 2GB. Signed-off-by: Nikolay Nikolaev <[email protected]>
We're passing this to the Makefile and then also in the Dockerfile. The result is calling the `bazel build --configure=release_debug` Signed-off-by: Nikolay Nikolaev <[email protected]>
We move the common image release workflow to a shareadble YAML and parametrize it. Then we include it in a release and release-debug YAML files. Signed-off-by: Nikolay Nikolaev <[email protected]>
83ae831 to
cc79648
Compare
This adds the bazel and make infrastructure to build release images with included symbols information.
It would be useful in production environments when debugging issues.
To leverage the build with CI, we move the core Release build functionality to
build-envoy-images-release-base.yamland then include it in the two new files:build-envoy-images-release.yaml- invoked on push in the branchbuild-envoy-images-release-debug.yaml- invoked on demand in the Actions UI