Add custom dm upload script to be used by the android framework

Add custom dm upload script to be used by the android framework

Committed: https://skia.googlesource.com/skia/+/7bdc8dfaabdee59d1961a390418ae6aafe0f9e62

[djsollen, 2015-03-05 13:55:01]

djsollen@google.com changed reviewers:
+ borenet@google.com, stephana@google.com

[borenet, 2015-03-05 15:48:47]

https://codereview.chromium.org/979153002/diff/1/platform_tools/android/trade...
File platform_tools/android/tradefed/upload_dm_results.py (right):

https://codereview.chromium.org/979153002/diff/1/platform_tools/android/trade...
platform_tools/android/tradefed/upload_dm_results.py:7: 
Nit: 2 lines between top-level items.

https://codereview.chromium.org/979153002/diff/1/platform_tools/android/trade...
platform_tools/android/tradefed/upload_dm_results.py:49: #
/dm-json-v1/year/month/day/hour/git-hash/builder/build-number/dm.json
This is not accurate.  Why aren't we using the commit hash?  Isn't that critical
for associating pairing new/bad images with commits?

[djsollen, 2015-03-05 15:52:26]

https://codereview.chromium.org/979153002/diff/1/platform_tools/android/trade...
File platform_tools/android/tradefed/upload_dm_results.py (right):

https://codereview.chromium.org/979153002/diff/1/platform_tools/android/trade...
platform_tools/android/tradefed/upload_dm_results.py:7: 
On 2015/03/05 15:48:47, borenet wrote:
> Nit: 2 lines between top-level items.

Done.

https://codereview.chromium.org/979153002/diff/1/platform_tools/android/trade...
platform_tools/android/tradefed/upload_dm_results.py:49: #
/dm-json-v1/year/month/day/hour/git-hash/builder/build-number/dm.json
On 2015/03/05 15:48:47, borenet wrote:
> This is not accurate.  Why aren't we using the commit hash?  Isn't that
critical
> for associating pairing new/bad images with commits?

Updated the comment.  Also we don't need the git hash here as Android will have
custom ingestion pipeline into gold that will convert the buildID into what is
necessary for gold (e.g. git_hash).

[borenet, 2015-03-05 15:53:56]

This LGTM but Stephan should probably take a look as well.

https://codereview.chromium.org/979153002/diff/1/platform_tools/android/trade...
File platform_tools/android/tradefed/upload_dm_results.py (right):

https://codereview.chromium.org/979153002/diff/1/platform_tools/android/trade...
platform_tools/android/tradefed/upload_dm_results.py:49: #
/dm-json-v1/year/month/day/hour/git-hash/builder/build-number/dm.json
On 2015/03/05 15:52:26, djsollen wrote:
> On 2015/03/05 15:48:47, borenet wrote:
> > This is not accurate.  Why aren't we using the commit hash?  Isn't that
> critical
> > for associating pairing new/bad images with commits?
> 
> Updated the comment.  Also we don't need the git hash here as Android will
have
> custom ingestion pipeline into gold that will convert the buildID into what is
> necessary for gold (e.g. git_hash).

Ok.

[djsollen, 2015-03-05 16:59:30]

The CQ bit was checked by djsollen@google.com

[commit-bot: I haz the power, 2015-03-05 16:59:43]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/979153002/20001

[commit-bot: I haz the power, 2015-03-05 17:14:01]

Committed patchset #2 (id:20001) as
https://skia.googlesource.com/skia/+/7bdc8dfaabdee59d1961a390418ae6aafe0f9e62

[stephana, 2015-03-05 18:53:22]

On 2015/03/05 17:14:01, I haz the power (commit-bot) wrote:
> Committed patchset #2 (id:20001) as
> https://skia.googlesource.com/skia/+/7bdc8dfaabdee59d1961a390418ae6aafe0f9e62

lgtm