Bug 1596354 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
The custom json schema validation from this [Github PR](https://github.com/mozilla/treeherder/pull/5319), written in Python, needs to be mirrored on `mozilla-central`.

I don't say this is the best approach *(I'm definitely not a fan of copy/pasting source code from one place to another)*, but we need this validation mechanic to be available there as well, for early erroring. This allows developers to quickly see if their data producers are working as expected.

In time, we need to find a way to properly share the [performance-artifact.json](https://github.com/mozilla/treeherder/blob/master/schemas/performance-artifact.json) schema *(+ plus any other extra validation)* between Perfherder and `mozilla-central`. Either employ a web microservice or a custom third party package etc
Revision 1 by
on 
The custom json schema validation from this [Github PR](https://github.com/mozilla/treeherder/pull/5319), written in Python, needs to be mirrored on `mozilla-central`. This ticket ensures bug 1572516 is entirely & properly done.

I don't say this is the best approach *(I'm definitely not a fan of copy/pasting source code from one place to another)*, but we need this validation mechanic to be available there as well, for early erroring. This allows developers to quickly see if their data producers are working as expected.

In time, we need to find a way to properly share the [performance-artifact.json](https://github.com/mozilla/treeherder/blob/master/schemas/performance-artifact.json) schema *(+ plus any other extra validation)* between Perfherder and `mozilla-central`. Either employ a web microservice or a custom third party package etc
Revision 2 by
on 
The custom json schema validation from this [Github PR](https://github.com/mozilla/treeherder/pull/5319), written in Python, needs to be mirrored on `mozilla-central`. This ticket ensures bug 1572516 is entirely & properly done.

I don't say this is the best approach *(I'm definitely not a fan of copy/pasting source code from one place to another)*, but we need this validation mechanic to be available there as well, for early erroring. It allows developers to quickly see if their data producers are working as expected.

In time, we need to find a way to properly share the [performance-artifact.json](https://github.com/mozilla/treeherder/blob/master/schemas/performance-artifact.json) schema *(+ plus any other extra validation)* between Perfherder and `mozilla-central`. Either employ a web microservice or a custom third party package etc
Revision 3 by
on 
The custom json schema validation from this [Github PR](https://github.com/mozilla/treeherder/pull/5319), written in Python, needs to be mirrored on `mozilla-central`. This ticket ensures bug 1572516 is entirely & properly done.

I don't say this is the best approach *(I'm definitely not a fan of copy/pasting source code from one place to another)*, but we need this validation mechanic to be available there as well, for early erroring. It allows developers to quickly see if their data producers are working as expected.

In time, we need to find a way to properly share the [performance-artifact.json](https://github.com/mozilla/treeherder/blob/master/schemas/performance-artifact.json) schema *(+ plus any other extra validation)* between Perfherder and `mozilla-central`. Either export this validation in a web microservice or a custom third party package etc

Back to Bug 1596354 Comment 0