Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(269)

Unified Diff: recipe_modules/bot_update/resources/bot_update.py

Issue 2311673002: Just disable force to ensure that bot_update really is running everywhere. (Closed)
Patch Set: Created 4 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: recipe_modules/bot_update/resources/bot_update.py
diff --git a/recipe_modules/bot_update/resources/bot_update.py b/recipe_modules/bot_update/resources/bot_update.py
index f8ecdb79f217cd2a396b34ab987ac3959aeb0a41..d3e9dbef4b0d2203255b2aeb9f7dd7a4d0bee819 100755
--- a/recipe_modules/bot_update/resources/bot_update.py
+++ b/recipe_modules/bot_update/resources/bot_update.py
@@ -1698,10 +1698,9 @@ def main():
slave = options.slave_name
master = options.master
- if not master:
- # bot_update activation whitelist is checked only on buildbot masters.
- # If there is no master, bot_update is always active.
- options.force = True
+ # Always run. This option will be removed in a later CL, but for now make sure
+ # that bot_update is ALWAYS set to run, no matter what.
+ options.force = True
# Check if this script should activate or not.
active = options.force or check_valid_host(master, builder, slave)
« no previous file with comments | « recipe_modules/bot_update/example.expected/tryjob_v8_head_by_default.json ('k') | recipe_modules/bot_update/test_api.py » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698