Add TRSS parser (#2190)

* Add TRSS parser

* Update Triage.md

Co-authored-by: George Adams <george.adams@microsoft.com>

Author: karianna

.gitignore

@@ -25,3 +25,4 @@ openjdk/*.gz
 /.classpath
 /.project
 /job.properties
+.vscode/

doc/Triage.md

@@ -1,24 +1,41 @@
 # Test Triage at AdoptOpenJDK
 
+## TRSS Parser for Release Builds
+
+We've created a NodeJS module to parse TRSS output, convert it to Markdown so folks can paste that summary into a GitHub issue.
+
+```bash
+npm install -g trss-parser
+trss-parser <parent id of TRSS pipeline run>
+```
+
 ## Triage Guidance
 
-There are many different test jobs running at the AdoptOpenJDK project.  No matter which test jobs are being triaged, there is a straight-forward pattern to follow: 
-#### Categorize the test failure (based on test output) into 1 of 3 general types: 
+There are many different test jobs running at the AdoptOpenJDK project.  No matter which test jobs are being triaged, there is a straight-forward pattern to follow.
+
+### Categorize the test failure (based on test output) into 1 of 3 general types
+
 - infra problem (machine/network)
 - test problem
-- product problem 
-#### Check for an existing issue 
-- if issue already exists for the failure, annotate with additional information if needed.  For example, if you are investigating failures in openjdk tests, look to see if its already reported in JBS, as per instructions in [Guidance for creating OpenJDK bugs](https://github.com/AdoptOpenJDK/openjdk-tests/wiki/Guidance-for-Creating-OpenJDK-Test-Defects). 
-#### Raise an issue if no issue exists
+- product problem
+
+### Check for an existing issue
+
+- if issue already exists for the failure, annotate with additional information if needed.  For example, if you are investigating failures in openjdk tests, look to see if its already reported in JBS, as per instructions in [Guidance for creating OpenJDK bugs](https://github.com/AdoptOpenJDK/openjdk-tests/wiki/Guidance-for-Creating-OpenJDK-Test-Defects).
+
+### Raise an issue if no issue exists
+
 - infra issue - raise an issue in [openjdk-infrastructure](https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues)
-- test issue - ideally, there are enough details to determine which test repo to raise an issue in ond of the test repos from which test material is pulled (OpenJDK, [openjdk-systemtest](https://github.com/AdoptOpenJDK/openjdk-systemtest/issues), [openjdk-tests](https://github.com/AdoptOpenJDK/openjdk-tests/issues) or any of the various 3rd party application suites).  If in doubt, ask some questions in the [#testing channel](https://adoptopenjdk.slack.com/messages/C5219G28G) and/or raise in [openjdk-tests](https://github.com/AdoptOpenJDK/openjdk-tests/issues) where it will get routed to proper repo
-  - OpenJDK test issues - see [Guidance for creating OpenJDK bugs](https://github.com/AdoptOpenJDK/openjdk-tests/wiki/Guidance-for-Creating-OpenJDK-Test-Defects) 
+- test issue - ideally, there are enough details to determine which test repo to raise an issue in ond of the test repositories from which test material is pulled (OpenJDK, [openjdk-systemtest](https://github.com/AdoptOpenJDK/openjdk-systemtest/issues), [openjdk-tests](https://github.com/AdoptOpenJDK/openjdk-tests/issues) or any of the various 3rd party application suites).  If in doubt, ask some questions in the [#testing channel](https://adoptopenjdk.slack.com/messages/C5219G28G) and/or raise in [openjdk-tests](https://github.com/AdoptOpenJDK/openjdk-tests/issues) where it will get routed to proper repo
+  - OpenJDK test issues - see [Guidance for creating OpenJDK bugs](https://github.com/AdoptOpenJDK/openjdk-tests/wiki/Guidance-for-Creating-OpenJDK-Test-Defects)
   - Additional guidance for external tests - [Triage Rules for Application tests](https://github.com/AdoptOpenJDK/openjdk-tests/tree/master/external#triage-rules)
 - product issue - additional steps may be necessary, before raising an issue
   - rerun the test - locally or using a Grinder: see [How to Run a Grinder wiki](https://github.com/AdoptOpenJDK/openjdk-tests/wiki/How-to-Run-a-Grinder-Build-on-Jenkins)
   - determine if the problem is occurs in other jdk versions, implementations and on other platforms
-  - if only observed against 1 implementation, raise an issue against that implementation in the correct upstream repo (typically either OpenJDK or [Eclipse OpenJ9](https://github.com/eclipse/openj9/issues) projects).  
-#### Exclude the test
+  - if only observed against 1 implementation, raise an issue against that implementation in the correct upstream repo (typically either OpenJDK or [Eclipse OpenJ9](https://github.com/eclipse/openj9/issues) projects).
+
+### Exclude the test
+
 - exclude in the most minimal way possible, if failing only on 1 platform, version or implementation, only exclude for that instance
 - put the full link to the associated open issue into the exclude file
 - exclude files vary depending on what test group you are triaging, refer to the README files in the openjdk-tests subdirectories for more details