Add wrapper for "gcl try"

Add wrapper for "gcl try"

Adds some validation for --bot
Committed: https://code.google.com/p/skia/source/detail?r=7315

[EricB, 2013-01-22 17:11:54]

Addresses some of the issues in the suggestions doc.  I'm hoping that this can
also wrap git-cl try in the future.

[rmistry, 2013-01-22 17:15:53]

https://codereview.appspot.com/7179048/diff/1/tools/gcl_try
File tools/gcl_try (right):

https://codereview.appspot.com/7179048/diff/1/tools/gcl_try#newcode7
tools/gcl_try:7: """ skia_try: Submit a try request. This is a thin wrapper
around "gcl try"
I think the convention is to have a single description line and then anything
more is in the next paragraph:

""" skia_try: Submit a try request.

This is a thing wrapper....
"""

https://codereview.appspot.com/7179048/diff/1/tools/gcl_try#newcode20
tools/gcl_try:20: SKIA_BUILD_MASTER_HOST = '70.32.156.51'
This is going to be difficult to maintain since we cannot share it with
buildbot, this IP is going to change in the very near future it is very likely
that we will forget to update this. Does this have to belong in trunk/tools ?

[EricB, 2013-01-22 17:40:39]

Patch set 2.

https://codereview.appspot.com/7179048/diff/1/tools/gcl_try
File tools/gcl_try (right):

https://codereview.appspot.com/7179048/diff/1/tools/gcl_try#newcode7
tools/gcl_try:7: """ skia_try: Submit a try request. This is a thin wrapper
around "gcl try"
On 2013/01/22 17:15:53, rmistry wrote:
> I think the convention is to have a single description line and then anything
> more is in the next paragraph:
> 
> """ skia_try: Submit a try request.
> 
> This is a thing wrapper....
> """

Done.

https://codereview.appspot.com/7179048/diff/1/tools/gcl_try#newcode20
tools/gcl_try:20: SKIA_BUILD_MASTER_HOST = '70.32.156.51'
On 2013/01/22 17:15:53, rmistry wrote:
> This is going to be difficult to maintain since we cannot share it with
> buildbot, this IP is going to change in the very near future it is very likely
> that we will forget to update this. Does this have to belong in trunk/tools ?

I had similar thoughts.  This has to go somewhere in trunk, since it will be
used by developers who don't have buildbot/ checked out.

What if we put a file somewhere in our checkout called skia_master_host and put
the ip there?  Then all scripts which need to communicate with the master can
query that file, either through the filesystem or http from googlecode.

[rmistry, 2013-01-22 18:20:30]

LGTM

As discussed, we should extract constants that we would like to share between
trunk and buildbot into a JSON file that will be parsed by both code bases (for
trunk the JSON file will be hosted on code.google.com).

[EricB, 2013-01-22 18:24:18]

On 2013/01/22 18:20:30, rmistry wrote:
> LGTM
> 
> As discussed, we should extract constants that we would like to share between
> trunk and buildbot into a JSON file that will be parsed by both code bases
(for
> trunk the JSON file will be hosted on http://code.google.com).

Filed https://code.google.com/p/skia/issues/detail?id=1081.

Committed as r7315.