Skip to content

Conversation

@nickolaev
Copy link

@nickolaev nickolaev commented Nov 16, 2025

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.yaml and then include it in the two new files:

  • build-envoy-images-release.yaml - invoked on push in the branch
  • build-envoy-images-release-debug.yaml - invoked on demand in the Actions UI

@nickolaev nickolaev changed the base branch from main to v1.34 November 16, 2025 19:33
@nickolaev nickolaev marked this pull request as ready for review November 19, 2025 17:35
@nickolaev nickolaev requested a review from a team as a code owner November 19, 2025 17:35
@nickolaev nickolaev requested a review from sayboras November 19, 2025 17:35
@@ -0,0 +1,10 @@
name: Refresh test & build cache & build latest
Copy link
Contributor

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.

Copy link
Author

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

@nickolaev nickolaev force-pushed the v1.34_debug branch 3 times, most recently from 407aa9b to 83ae831 Compare November 21, 2025 10:24
@sayboras
Copy link
Member

sayboras commented Dec 3, 2025

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.

@nickolaev
Copy link
Author

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 :)
I will move it to main now. Thanks!

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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants