[Linaro-validation] using latest lava-android-test

[Michael Hudson-Doyle]

Andy Doan <andy.doan at linaro.org> writes:

>  From IRC earlier:
>
> <liuyq> asac, :( it will not work now, the branches has not been 
> deployed. Also I haven't merged yet:(
>
> <asac> liuyq: we have to always deployt? thought we always pull latest 
> from bzr
> <asac> we should always have access to all the latest tests without 
> another deploy step
> <asac> doanac: ^^ new requirement it seems
>
> I wanted to discuss here and make sure I'm clear. We basically need to 
> stop using the lava-android-test published to pip and start always 
> pulling lava-android-test from trunk?

lava-android-test is a server side component just like lava-server or
lava-dashboard or anything else.  I'm pretty opposed to deploying it
in a different way than the other bits!  We talked yesterday about how
we should be deploying more things from branches, but I still think
there should be a human in the loop between trunk and deployment
especially with the almost total lack of pre-merge testing we have
today...

Cheers,
mwh