pub struct RunnerBuildReq {Show 14 fields
pub arch: Option<String>,
pub args: Option<HashMap<String, String>>,
pub binaries: Option<Vec<BinarySpec>>,
pub branch: Option<String>,
pub bucket: Option<String>,
pub context: Option<String>,
pub docker_target: Option<String>,
pub dockerfile: Option<String>,
pub image: Option<String>,
pub os: Option<String>,
pub ref: Option<String>,
pub repo: Option<String>,
pub sha: Option<String>,
pub tag: Option<String>,
}Fields§
§arch: Option<String>Arch is the target architecture for the artifact lane.
args: Option<HashMap<String, String>>Args are –build-arg values. They are what lets several images off ONE Dockerfile mean different things — the sandbox classes are three entries differing only by STAGE. Validated at the k8s choke point, with VERSION and REVISION taking precedence: those are receipts the builder derives from the tag and the commit, and a caller that could overwrite them could make an image lie about which commit it is.
binaries: Option<Vec<BinarySpec>>Binaries selects the ARTIFACT lane (artifact.go): build what the repo’s hanzo.yml binaries: block declares — a Go binary, an npm tarball, a Rust binary — and publish it to hanzoai/s3 instead of pushing an image. It is the same recipe hanzoai/ci reads, sent verbatim, so image is meaningless here and must be absent.
branch: Option<String>Branch is the branch to build when no SHA or Ref is given.
bucket: Option<String>Bucket mirrors hanzo.yml’s bucket: — where the artifact lane publishes.
context: Option<String>Context is the build context path within the repo.
docker_target: Option<String>DockerTarget is the multi-stage build target to stop at.
dockerfile: Option<String>Dockerfile is the path to build from; empty uses the zero-config frontend.
image: Option<String>Image is the output image ref to push. Required on the image lane, and it must target a registry namespace the caller’s org owns.
os: Option<String>OS is the target operating system for the artifact lane.
ref: Option<String>Ref is the git ref to build when no SHA is given.
repo: Option<String>Repo is the repository clone URL to build. Required on the image lane.
sha: Option<String>SHA is the commit to pin; it wins over Ref and Branch.
tag: Option<String>Tag is the publish path segment, so both entry points write ONE index at ONE URL. It defaults to the pinned ref, and must be named explicitly for a branch.
Implementations§
Source§impl RunnerBuildReq
impl RunnerBuildReq
pub fn new() -> RunnerBuildReq
Trait Implementations§
Source§impl Clone for RunnerBuildReq
impl Clone for RunnerBuildReq
Source§fn clone(&self) -> RunnerBuildReq
fn clone(&self) -> RunnerBuildReq
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more