You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
class BuildDocker,PrepareBinaries,AttachBinaries primary
80
84
class ReleaseWorkflow,ReleaseBinaries primary
81
85
class Unit,Lint,Coverage,DockerCfg,CrateBuild,PRGate,Docs,Security secondary
82
86
class IT,FindDisks,Deploy,DeployNodes,Cleanup secondary
@@ -138,7 +142,40 @@ _The diagram above illustrates the parallel execution patterns in our CI/CD syst
138
142
139
143
**Note**: Self-hosted Runners are just used to keep the logs running in the GitHub Actions UI for over 6 hours, the Integration Tests are not run in the Self-hosted Runner itself, but in the deployed VMs in GCP through GitHub Actions.
140
144
141
-
### 5. Queue Management
145
+
### 5. Rust build caching
146
+
147
+
Rust jobs cache `~/.cargo` and dependency artifacts in `target/` through
-**Release** (`release.yml`): Creates or updates Release PRs with release-plz, then uses `ZcashFoundation/cargo-release` and native Cargo to reconcile crates, tags, and one `zebrad` GitHub Release. See the [release process](../../book/src/dev/release-process.md#release-candidate--release-process) for operational instructions.
163
-
-**Release Binaries** (`release-binaries.yml`): Build and publish release artifacts
200
+
-**Release Binaries** (`release-binaries.yml`): Orchestrates release images, prepares and attaches downloadable binaries, and supports manual preparation validation without release attachment
0 commit comments