On 21 June 2011 14:10, Paul Larson paul.larson@linaro.org wrote:
On Mon, Jun 20, 2011 at 9:35 PM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Frans is going to work to pull these together. There's a BP at:
https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-connect...
-Zach
On 20 June 2011 18:47, Michael Hudson-Doyle michael.hudson@linaro.org wrote:
The build should also probably wait until the test is done and get a pass fail, this should help set us up for Gerrit integration in the near future.
I guess the naive implementation of this would leave the EC2 instance running while the test runs which would be wasteful... but that's something for Paul to figure out.
Would that really be necessary? Or does the process go more like:
- topic branch created with testing requested, intended for inclusion if
everything is ok 2. do testing 3. if tests pass, merge (is this manual?)
Yeah. That sync's up with the Gerrit flow: http://source.android.com/source/life-of-a-patch.html
The blueprint mentioned doesn't seem to cover the reverse path for Gerrit to somehow interpret those test results and do something with them. Should it? If so, I think we need to better understand how that piece works from the Gerrit side.
Lets mumble about this.
Thanks, Paul Larson