tuwunel/.github/workflows
Jason Volk deb5c65885 docker: Add conditions to set assert_linkage for Dockerfile.install
ci: Check packages when using test branch.

Signed-off-by: Jason Volk <jason@zemos.net>
2025-11-23 03:36:17 +00:00
..
bake.yml ci: Add multi-runner/multi-arch to matrices. (closes #55) 2025-06-17 03:41:27 +00:00
lint.yml ci: Re-enable lychee. 2025-11-18 10:47:59 +00:00
main.yml docker: Add conditions to set assert_linkage for Dockerfile.install 2025-11-23 03:36:17 +00:00
package.yml ci: Extract Nix artifacts. 2025-10-27 09:39:57 +00:00
publish.yml ci: Fix pages deployment. (#165) 2025-09-23 05:15:10 +00:00
README.md docker: Simplify build/install; dedup cargo commands; enable gc. 2025-06-04 03:44:21 +00:00
test.yml docker: Move complement logs into tests directory. 2025-11-18 19:29:21 +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.