[Tree Status] Update all references in Skia repo to tree-status

* Mainly updates to documentation.
* Fix some comments in PRESUBMIT.py.
* Delete tools/lua/trigger_ct_lua. It has not worked in many years.

Bug: skia:9962
Change-Id: If6f58f173f2c8bd3fc9bdfc4db440f42489fee08
Docs-Preview: https://skia.org/?cl=274597
Reviewed-on: https://skia-review.googlesource.com/c/skia/+/274597
Commit-Queue: Ravi Mistry <rmistry@google.com>
Reviewed-by: Eric Boren <borenet@google.com>

Author: rmistry

PRESUBMIT.py

@@ -282,11 +282,7 @@ def _CommonChecks(input_api, output_api):
 
 
 def CheckChangeOnUpload(input_api, output_api):
-  """Presubmit checks for the change on upload.
-
-  The following are the presubmit checks:
-  * Check change has one and only one EOL.
-  """
+  """Presubmit checks for the change on upload."""
   results = []
   results.extend(_CommonChecks(input_api, output_api))
   # Run on upload, not commit, since the presubmit bot apparently doesn't have
@@ -524,14 +520,7 @@ def PostUploadHook(gerrit, change, output_api):
 
 
 def CheckChangeOnCommit(input_api, output_api):
-  """Presubmit checks for the change on commit.
-
-  The following are the presubmit checks:
-  * Check change has one and only one EOL.
-  * Ensures that the Skia tree is open in
-    http://skia-tree-status.appspot.com/. Shows a warning if it is in 'Caution'
-    state and an error if it is in 'Closed' state.
-  """
+  """Presubmit checks for the change on commit."""
   results = []
   results.extend(_CommonChecks(input_api, output_api))
   results.extend(_CheckLGTMsForPublicAPI(input_api, output_api))

infra/bots/android_compile/trigger_wait_ac_task.py

@@ -34,7 +34,7 @@
       '\n\n'
       'Your run failed due to unknown infrastructure failures.\n'
       'Please contact rmistry@ or the trooper from '
-      'http://skia-tree-status.appspot.com/trooper\n'
+      'http://tree-status.skia.org/trooper\n'
       'Sorry for the inconvenience!\n'
 )
 

infra/bots/g3_compile/trigger_wait_g3_task.py

@@ -31,7 +31,7 @@
     '\n\n'
     'Your run failed due to unknown infrastructure failures.\n'
     'Please contact rmistry@ or the trooper from '
-    'http://skia-tree-status.appspot.com/trooper\n'
+    'http://tree-status.skia.org/trooper\n'
     'Sorry for the inconvenience!\n'
 )
 MISSING_APPROVAL_ERROR_MSG = (

site/dev/contrib/directory.md

@@ -15,7 +15,7 @@ The Skia Directory
 
 *   BuildBot Consoles
     -   [Commit Status](https://status.skia.org/)
-    -   [Tree Status](https://skia-tree-status.appspot.com/) (requires login)
+    -   [Tree Status](https://tree-status.skia.org/) (requires login)
     -   [BuildBot Console](https://build.chromium.org/p/client.skia/console)
     -   [FYI BuildBot
         Console](https://build.chromium.org/p/client.skia.fyi/console)

site/dev/sheriffing/android.md

@@ -53,7 +53,7 @@ The changes created by the release rollers:
 View current and upcoming RoboCops
 ----------------------------------
 
-The list of RoboCops is specified in the [skia-tree-status web app](http://skia-tree-status.appspot.com/robocop). The current RoboCop is highlighted in green.
+The list of RoboCops is specified in the [tree-status web app](http://tree-status.skia.org/robocop). The current RoboCop is highlighted in green.
 The banner on the top of the [status page](https://status.skia.org) also displays the current RoboCop.
 
 

site/dev/sheriffing/gpu.md

@@ -42,7 +42,7 @@ Also, whenever a wrangler figures out how to accomplish a wrangly task (e.g. run
 View current and upcoming wranglers
 ----------------------------------
 
-The list of wranglers is specified in the [skia-tree-status web app](http://skia-tree-status.appspot.com/gpu-sheriff). The current wrangler is highlighted in green.
+The list of wranglers is specified in the [tree-status web app](http://tree-status.skia.org/wrangler). The current wrangler is highlighted in green.
 The banner on the top of the [status page](https://status.skia.org) also displays the current wrangler.
 
 

site/dev/sheriffing/index.md

@@ -31,7 +31,7 @@ Below is a brief summary of what the sheriff does for each task:
 * Understand the [testing infrastructure](https://skia.org/dev/testing/automated_testing).
 * Start watching the [status page](https://status.skia.org) for bot breakages.
 * Track down people responsible for breakages and revert broken changes if there is no easy fix. You can use [blamer](#blamer) to help track down such changes.
-* Close and open the [tree](http://skia-tree-status.appspot.com).
+* Close and open the [tree](http://tree-status.skia.org).
 * Keep the builder comments on the [status page](https://status.skia.org) up to date.
 * File or follow up with [BreakingTheBuildbots bugs](https://bugs.chromium.org/p/skia/issues/list?q=label:BreakingTheBuildbots). See the tip on [when to file bugs](#when_to_file_bugs).
 * Read and update the [Ongoing Issues section](https://docs.google.com/document/d/1y2jUf4vXI0fwhu2TiCLVIfWC1JOxFcHXGw39y7i-y_I/edit#heading=h.tpualuc3p7z0) in the handoff doc.
@@ -80,7 +80,7 @@ In general, sheriffs should have a strong bias towards actions that keep the tre
 View current and upcoming sheriffs
 ----------------------------------
 
-The list of sheriffs is specified in the [skia-tree-status web app](https://skia-tree-status.appspot.com/sheriff). The current sheriff is highlighted in green.
+The list of sheriffs is specified in the [tree-status web app](https://tree-status.skia.org/sheriff). The current sheriff is highlighted in green.
 The banner on the top of the [status page](https://status.skia.org) also displays the current sheriff.
 
 
@@ -105,7 +105,7 @@ Look at all existing [BreakingTheBuildbots bugs](https://bug.skia.org/?q=label:B
 <a name="how_close_tree"></a>
 ### How to close or re-open the tree
 
-1. Go to [skia-tree-status.appspot.com](https://skia-tree-status.appspot.com).
+1. Go to [tree-status.skia.org](https://tree-status.skia.org).
 2. Change the status.
  *  To close the tree, include the word "closed" in the status.
  * To open the tree, include the word "open" in the status.

site/dev/testing/swarmingbots.md

@@ -69,7 +69,7 @@ a bug][infra bug] and assign to jcgregorio for reassignment.
 For your convenience, the machine skolo-builder is available for checking out and compiling code within the Skolo. See
 more info in the [Skolo maintenance doc][remote access] remote access section.
 
-[current trooper]: http://skia-tree-status.appspot.com/trooper
+[current trooper]: http://tree-status.skia.org/trooper
 [remote access]:
     https://docs.google.com/document/d/1zTR1YtrIFBo-fRWgbUgvJNVJ-s_4_sNjTrHIoX2vulo/edit#heading=h.v77cmwbwc5la
 [infra bug]: https://bugs.chromium.org/p/skia/issues/entry?template=Infrastructure+Bug

tools/lua/ngrams.lua

@@ -6,7 +6,7 @@
 -- $ lua tools/lua/ngrams_aggregate.lua
 
 -- To run on Cluster Telemetry, copy and paste the contents of this file into
--- the box at https://skia-tree-status.appspot.com/skia-telemetry/lua_script,
+-- the box at https://ct.skia.org/lua_script/,
 -- and paste the contents of ngrams_aggregate.lua into the "aggregator script"
 -- box on the same page.