Just disable force to ensure that bot_update really is running everywhere.
This makes it so that regardless of what force is set to in the recipe, if you invoke bot_update.ensure_checkout, it will actually run. Removal of the force option (and related options) to come shortly. R=estaab@chromium.org, hinoka@chromium.org, martiniss@chromium.org, tandrii@chromium.org BUG=643885 Review-Url: https://codereview.chromium.org/2311673002changes/18/399118/1
iannucci
9 years ago
committed by
Commit bot
parent
274c159b29
commit
95f3d317e4
@ -1,43 +0,0 @@
|
||||
[
|
||||
{
|
||||
"cmd": [
|
||||
"python",
|
||||
"-u",
|
||||
"RECIPE_MODULE[depot_tools::bot_update]/resources/bot_update.py",
|
||||
"--master",
|
||||
"experimental",
|
||||
"--builder",
|
||||
"Experimental Builder",
|
||||
"--slave",
|
||||
"somehost",
|
||||
"--spec",
|
||||
"cache_dir = '[GIT_CACHE]'\nsolutions = [{'deps_file': '.DEPS.git', 'managed': True, 'name': 'src', 'url': 'https://chromium.googlesource.com/chromium/src.git'}]",
|
||||
"--root",
|
||||
"src",
|
||||
"--revision_mapping_file",
|
||||
"{\"src\": \"got_cr_revision\"}",
|
||||
"--git-cache-dir",
|
||||
"[GIT_CACHE]",
|
||||
"--output_json",
|
||||
"/path/to/tmp/json",
|
||||
"--revision",
|
||||
"src@HEAD"
|
||||
],
|
||||
"env": {
|
||||
"PATH": "%(PATH)s:RECIPE_PACKAGE_REPO[depot_tools]"
|
||||
},
|
||||
"name": "bot_update",
|
||||
"~followup_annotations": [
|
||||
"@@@STEP_LOG_LINE@json.output@{@@@",
|
||||
"@@@STEP_LOG_LINE@json.output@ \"did_run\": false, @@@",
|
||||
"@@@STEP_LOG_LINE@json.output@ \"patch_failure\": false@@@",
|
||||
"@@@STEP_LOG_LINE@json.output@}@@@",
|
||||
"@@@STEP_LOG_END@json.output@@@"
|
||||
]
|
||||
},
|
||||
{
|
||||
"name": "$result",
|
||||
"recipe_result": null,
|
||||
"status_code": 0
|
||||
}
|
||||
]
|
||||
Loading…
Reference in New Issue