Set up Blimp Integration script on FYI bot

Set up Blimp Integration script on FYI bot

Script: blimp/tools/client_engine_integration.py
Bot: chromium.fyi

Starts by 'client_engine_integration.py start'. Installs/loads after checking json file existing. Cleans up env in finally block.

Linked CL (Detach engine process): https://codereview.chromium.org/2283083002/

BUG=640368

[shenghuazhang, 2016-08-23 22:21:48]

Description was changed from

==========
Set up Blimp Integration script on FYI bot

BUG=640368
==========

to

==========
Set up Blimp Integration script on FYI bot

Script: blimp/tools/client_engine_integration.py
Bot: chromium.fyi

Starts by 'client_engine_integration.py start'. Installs/loads after checking
json file existing. Cleans up env in finally block.

BUG=640368
==========

[shenghuazhang, 2016-08-26 19:35:59]

Description was changed from

==========
Set up Blimp Integration script on FYI bot

Script: blimp/tools/client_engine_integration.py
Bot: chromium.fyi

Starts by 'client_engine_integration.py start'. Installs/loads after checking
json file existing. Cleans up env in finally block.

BUG=640368
==========

to

==========
Set up Blimp Integration script on FYI bot

Script: blimp/tools/client_engine_integration.py
Bot: chromium.fyi

Starts by 'client_engine_integration.py start'. Installs/loads after checking
json file existing. Cleans up env in finally block.

Linked CL (Detach engine process): https://codereview.chromium.org/2283083002/

BUG=640368
==========

[shenghuazhang, 2016-08-26 19:37:13]

shenghuazhang@chromium.org changed reviewers:
+ jbudorick@chromium.org

[jbudorick, 2016-08-26 21:22:38]

https://codereview.chromium.org/2269303002/diff/20001/scripts/slave/recipe_mo...
File scripts/slave/recipe_modules/chromium_tests/steps.py (right):

https://codereview.chromium.org/2269303002/diff/20001/scripts/slave/recipe_mo...
scripts/slave/recipe_modules/chromium_tests/steps.py:1765:
api.chromium.set_config('chromium', TARGET_PLATFORM='linux')
I don't think a Test step is the right place for the second compilation.

https://codereview.chromium.org/2269303002/diff/20001/scripts/slave/recipe_mo...
scripts/slave/recipe_modules/chromium_tests/steps.py:1773: blimp_apk_path =
api.path['checkout'].join('out-android', 'Debug', 'Blimp.apk')
wouldn't this be out-android/Debug/apks/Blimp.apk?

https://codereview.chromium.org/2269303002/diff/20001/scripts/slave/recipe_mo...
scripts/slave/recipe_modules/chromium_tests/steps.py:1786: api.python(
I'd like this to be a bit more general s.t. we can specify different things to
do between starting and stopping the engine. Not exactly sure how to do that,
though -- I'll think about it a bit and get back to you.

[jbudorick, 2016-09-13 02:44:33]

Sorry about the delay here.

After thinking about this more (and as we've discussed offline, albeit briefly),
I think that a dedicated recipe is better suited to the double build that this
has to do. We can probably use *some* of the same calls that
api.chromium_tests.main_waterfall_steps does -- create_bot_config_object,
configure_build, prepare_checkout, and get_tests should all be usable.
get-compile_targets and compile_specific_targets might be usable, though we'd
have to run them twice (unsurprisingly) and in different directories. It may be
simpler to call some of the things those functions call directly; I'm not sure.