Make PreCQ builds "Production Builds" |
||
Issue descriptionToday, PreCQ builds are launched with "--remote-tryjob" which means they are treated like manual tryjobs from developers. We currently connect PreCQ jobs to the production CIDB database via a special hack here: https://cs.corp.google.com/chromeos_public/chromite/scripts/cbuildbot.py?l=1008 But that means that PreCQ tryjobs are also connecting to the production CIDB. I think the PreCQ launcher should use "--production" tryjobs, and the PreCQ CIDB hack should be removed. This allows a clean distinction between test/production builds, and allows PreCQ builders to trust options.debug.
,
Sep 5 2017
This doesn't work. Sync stages of production builds explicitly refuse to cherry-pick in changes for safety reasons. In every other case, I agree with that test, so I'm not going to override it here. I'll come up with another way to distinguish 'production' tryjobs for 'tryjob' tryjobs.
,
Dec 15 2017
Closing, since there are new approaches covered under other bugs. |
||
►
Sign in to add a comment |
||
Comment 1 by dgarr...@chromium.org
, Sep 5 2017