Add a segment about bin/try to the site docs

No-Try: true
Docs-Preview: https://skia.org/?cl=60586
Bug: skia:
Change-Id: I8169d4199564380cc602e0c46a5d4fadd1c28dcb
Reviewed-on: https://skia-review.googlesource.com/60586
Reviewed-by: Ravi Mistry <rmistry@google.com>
Commit-Queue: Eric Boren <borenet@google.com>

2 files changed, 35 insertions, 8 deletions

diff --git a/site/dev/contrib/submit.md b/site/dev/contrib/submit.md
index d3ffc9d572..4dd380d77a 100644
--- a/site/dev/contrib/submit.md
+++ b/site/dev/contrib/submit.md
@@ -93,6 +93,27 @@ The command output should include a URL, similar to
 (https://skia-review.googlesource.com/c/4559/), indicating where your changelist
 can be reviewed.
 
+### Submit try jobs
+
+Skia's trybots allow testing and verification of changes before they land in the
+repo. You need to have permission to trigger try jobs; if you need permission,
+ask a committer. After uploading your CL to [Gerrit](https://skia-review.googlesource.com/),
+you may trigger a try job for any job listed in tasks.json, either via the
+Gerrit UI, using "git cl try", eg.
+
+    git cl try -B skia.primary -b Some-Tryjob-Name
+
+or using bin/try, a small wrapper for "git cl try" which helps to choose try jobs.
+From a Skia checkout:
+
+    bin/try --list
+
+You can also search using regular expressions:
+
+    bin/try "Test.*GTX660.*Release"
+
+For more information about testing, see [testing infrastructure](https://skia.org/dev/testing/automated_testing).
+
 ### Request review
 
 Go to the supplied URL or go to the code review page and select the **Your**
diff --git a/site/dev/testing/automated_testing.md b/site/dev/testing/automated_testing.md
index e45e3dba5c..8fb64cc8ad 100644
--- a/site/dev/testing/automated_testing.md
+++ b/site/dev/testing/automated_testing.md
@@ -41,16 +41,22 @@ file is up to date:
 Try Jobs
 --------
 
-It is useful to know how your change will perform before it is submitted. After
-uploading your CL to [Gerrit](https://skia-review.googlesource.com/), you may
-trigger a try job for any job listed in tasks.json:
+Skia's trybots allow testing and verification of changes before they land in the
+repo. You need to have permission to trigger try jobs; if you need permission,
+ask a committer. After uploading your CL to [Gerrit](https://skia-review.googlesource.com/),
+you may trigger a try job for any job listed in tasks.json, either via the
+Gerrit UI, using "git cl try", eg.
 
-	$ git cl try -B <bucket name> -b <job name>
+    git cl try -B skia.primary -b Some-Tryjob-Name
 
-The bucket name refers to the [Buildbucket](https://chromium.googlesource.com/infra/infra/+/master/appengine/cr-buildbucket/README.md)
-bucket to which the request will be submitted. Most public Skia repos use the
-"skia.primary" bucket, and most private Skia repos use the "skia.internal"
-bucket.
+or using bin/try, a small wrapper for "git cl try" which helps to choose try jobs.
+From a Skia checkout:
+
+    bin/try --list
+
+You can also search using regular expressions:
+
+    bin/try "Test.*GTX660.*Release"
 
 
 Status View