CQ: skip a builder in dryrun |
|||
Issue descriptionCrOS would like to skip expensive HWTests in CQ dryrun. HWTests is step(s) in a pre-submit builder, so we'd need to pass the dryrun flag to the build, perhaps as a property. FWIU this should be a non-default behavior, otherwise by default we cannot reuse a dry build for a non-dry run. Perhaps we need a builder-level setting in cq.cfg to pass the flag. This blocks CrOS adoption of CQ. assigning to triage.
,
Nov 28
after chatting more, we figured that it would be simpler to do the following instead: - have two variants of each builder: hw and non-hw. They are independent and no reuse each other's work. - CQ skips hw in dryrun it is better because a green build of builder X clearly says whether HW were included. Gerrit wouldn't combine hw and non-hw builds into one block. so looks like instead we just need a per-builder boolean flag in cq.cfg that instructs CQ to skip the builder in dryrun mode.
,
Nov 29
I like this idea, perhaps a dry run enum with values: ALSO // default, means also run in dry run SKIP // skips in dry run, but runs in full run. ONLY // only run during dry run. Btw, you logic about UI also applies to special presubmit builders, which do different things during dry run.
,
Dec 4
|
|||
►
Sign in to add a comment |
|||
Comment 1 by no...@chromium.org
, Nov 28