Changes to CI Performance/Perfherder Data Ingestion

[Gregory Mierzwinski]

Hello,

Over the last couple months, we've been working on moving all of our performance/perfherder data ingestion away from log-based parsing to JSON artifact-based parsing. This is a prerequisite for ingesting all performance data replicates/trials into our DB across all of our CI branches.

Currently, log-based parsing checks the CI task logs for lines that contain `PERFHERDER_DATA` and then parses and validates the JSON-formatted results from that line to ingest into our performance data database in Treeherder. In the very near future, we will instead be ingesting artifacts that contain the keyword `perfherder-data` in their name to parse and validate for performance data to add to the database.

Apart from fetch-content `PERFHERDER_DATA` log outputs which requires some additional fixes, all logging output for performance data should now have an associated `perfherder-data-*.json` artifact being produced for ingestion. You can follow this bug for additional progress.

If you've added any new `PERFHERDER_DATA` log outputs in the last 1-2 months, please ensure that there is also a `perfherder-data-*.json` file being output alongside it. If you see any performance data logs being generated that do not have an associated JSON artifact, please let either myself (:sparky), or Myeongjun Go (:myeongjun) know about this, or feel free to file a bug about it in the Testing :: Performance component.

If there are any additional questions, concerns, etc. feel free to ping us about it.

Thank you,

Greg