romenskiy2012/tuwunel
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
tuwunel/.github/workflows
History
Jason Volk a86bb8b8c7 Start a README in the github workflow directory. 
Tweaks to docker readme.

Tweaks to main readme.

Signed-off-by: Jason Volk <jason@zemos.net>
2025-05-31 08:16:21 +00:00
..
bake.yml ci: Abstract artifact uploads for every bake target. 2025-05-29 20:16:06 +00:00
deps.yml ci: yaml formatting. 2025-05-29 20:16:06 +00:00
lint.yml ci: yaml formatting. 2025-05-29 20:16:06 +00:00
main.yml ci: comment-out deps job (see github.com/orgs/community/discussions/18001) 2025-05-29 20:16:06 +00:00
package.yml ci: Abstract artifact uploads for every bake target. 2025-05-29 20:16:06 +00:00
publish.yml ci: Abstract artifact uploads for every bake target. 2025-05-29 20:16:06 +00:00
README.md Start a README in the github workflow directory. 2025-05-31 08:16:21 +00:00
test.yml docker: Build rocksdb native for release-max-perf. 2025-05-22 08:03:28 +00:00

README.md

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 frameworks 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.