Commit history with code coverage summary

[mozilla]

Commit history with code coverage summary

[armenzg]

I'm currently trying to fetch this API with codecov:
https://codecov.io/api/gh/marco-c/gecko-dev/commits

I believe I need an access token so I can use it:
https://docs.codecov.io/v4.3.6/reference#authorization

I'm currently hitting:

No 'Access-Control-Allow-Origin' header is present on requested resource

For now I will make this work locally by serving the file locally. It won't work on GitHub pages until I have an access token from marco.

[armenzg]

Until there is a solution for issue #10 I can only show screenshots of the app.
I will wait until marco comes around and see if he can proxy that for me.

Here's the latest screenshot:
https://cl.ly/3n141N272k0u

It shows commits from https://codecov.io/api/gh/marco-c/gecko-dev/commits sorted by timestamp.

There's data in that API for me to show the code coverage for each commit.
I will work on that tomorrow.

[armenzg]

I put some effort into making the changes from yesterday "shareable" publicly.

In this effort, I ended up migrating us to Heroku:
https://firefox-code-coverage.herokuapp.com/#/

In any case, it was not the migration which allowed this to happen but to apply a hack:
4e1f44b

[armenzg]

Blocked on mozilla/release-services#594

I'm going to make progress on issue #3

[armenzg]

Until mozilla/release-services#632 gets fixed I will have to sequentially fetch for each push.

[marco-c]

When mozilla/release-services#632 is fixed, the performance will be the more or less the same (as the requests will be performed sequentially on the server instead of on the client).
So if fetching sequentially seems too slow, we will probably have to increase the number of web/worker processes on Heroku.

(We should only care about the performance for the common case, which is the cached responses case)

[armenzg]

We have accomplished this.
We will tackle having summary for each changeset later.