tuwunel/.github/workflows
Jason Volk 499991e530 Rename build profile release-max-perf to release-native.
Signed-off-by: Jason Volk <jason@zemos.net>
2025-06-06 02:10:04 +00:00
..
bake.yml docker: Refactor feat_set out of base layers. 2025-06-05 12:50:09 +00:00
deps.yml docker: Refactor feat_set out of base layers. 2025-06-05 12:50:09 +00:00
lint.yml ci: Workaround multi-line if-condition github bug; cleanup. 2025-06-01 21:13:26 +00:00
main.yml Rename build profile release-max-perf to release-native. 2025-06-06 02:10:04 +00:00
package.yml ci: Add oci image to pipeline. 2025-06-05 12:37:19 +00:00
publish.yml ci: Add oci image to pipeline. 2025-06-05 12:37:19 +00:00
README.md docker: Simplify build/install; dedup cargo commands; enable gc. 2025-06-04 03:44:21 +00:00
test.yml Rename build profile release-max-perf to release-native. 2025-06-06 02:10:04 +00:00

Overview

The release pipeline Main (main.yml) and its subroutines defined in the other yamls form a high-level description for the underlying self-hosted build system in /docker. In other words, this is a sort of terminal, a "thin-client" with a display and a keyboard for our docker mainframe. We minimize vendor-lockin and duplication with other services by limiting everything here to only what is essential for driving the docker builder.

Though we slightly relax the above by specifying details of the actual CI pipeline, the control-flow logic to go from some input event to some output or release here. This gives us better integration with github, like granular progress indications by breaking up operations as individual jobs and workflows within the pipeline. This means we'll have duplicate logic with other services, but only as it relates to high-level control flow.