Run buildbot slaves from a CIPD package |
||||||
Issue descriptionKey points here are: 1) Rollouts should be explicit, not automatic from HEAD. 2) Changes should be canaried on a small number of slaves first. 3) Rollbacks should still be possible if the package is broken (i.e. run_slave.py mustn't be responsible for updating the package). All these can be done by the deployment mechanism we're planning to use for CQ in issue 525077, so let's use the same one.
,
Mar 8 2017
,
Apr 26 2017
Any updates on this?
,
Jul 27 2017
,
Jun 2 2018
Friendly ping. Unassigning from Scott and CCing +jbudorick to comment. This is a cit-pm-30 blocking bug. Please update priority accordingly.
,
Jun 4 2018
This bug is really stale, and we're also planning to mass-migrate from Buildbot to LUCI at this point. I'll downgrade to P3 as part of Foundation triage, in the event that we still want this functionality for any builders not yet on LUCI. If anyone has additional context, please update as needed!
,
Jun 6 2018
Fun fact: All Win/Linux GCE Buildbot slaves run from CIPD packages But anyways, we're about to transition to LUCI, so any work put in this would becoming obsolete in ~2Q, marking this as WontFix |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by benhenry@chromium.org
, Jan 18 2017