-
Notifications
You must be signed in to change notification settings - Fork 0
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
REC-67: build release on Debian 11 #49
Conversation
Release binaries should not require glibc from Debian 12, we can use something a little older.
It looks like we haven't granted permissions for the Debian 11 images to CI runners yet. EDIT: now fixed. |
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.
LGTM % warning about switching to choice
@@ -21,17 +21,27 @@ on: | |||
type: string | |||
description: Version of engflow_auth to release; must be a semver version string, starting with `v` | |||
required: true | |||
dry_run: | |||
type: boolean |
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.
Warning: from my experience, boolean inputs don't work as expected in GHA: https://github.com/EngFlow/engflow/blob/dbd7172b5bf1bbce62f55ca0bab167bee42cd40c/.github/workflows/build-chromium-reclient.yml#L21
@minor-fixes - @jayconrod is out for the next 2.5 weeks, can you help merge and get released? |
Switched to a Debian 11 worker image so that we link against a glibc with a lower version.
Disabled remote execution for the release workflow because the currently release binaries
are linked against a higher version of glibc and don't run on Debian 11. Also some things
are not wired up correctly. We can turn this back on after the next release.
Added a "dry run" mode to the release workflow so it's easier to check if things are wired up
correctly in the future.