Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reduce coverage uploads to ease on codecov service #34487

Open
PVince81 opened this issue Feb 14, 2019 · 1 comment
Open

Reduce coverage uploads to ease on codecov service #34487

PVince81 opened this issue Feb 14, 2019 · 1 comment

Comments

@PVince81
Copy link
Contributor

Currently the codecov service is broken and reports cannot be opened for any PRs.
Am already in talk with codecov support.

From looking at drone.yml it seems we're uploading 13 coverage reports for every commit, and this might be triggering some API quota issues on their side.

Now I wonder if we really need that many reports ?
Or is there a way to combine them to reduce the number of uploads ?

It does look like the problem might have started after we moved everything from Travis to Drone. It is also possible that we increased the number of coverage uploads over a few months.

I haven't digged in exact history as I haven't been able to easily find old PRs where codecov still worked. Well, at least this one seemed to work: #29136 (comment)

@DeepDiver1975 @phil-davis @individual-it @patrickjahns

@PVince81 PVince81 added this to the backlog milestone Feb 14, 2019
@ownclouders
Copy link
Contributor

GitMate.io thinks the contributor most likely able to help you is @phil-davis.

Possibly related issues are #30206 (Use codecov bash to upload coverage information), #30675 (Add JS coverage to codecov), #18166 (Upload deduplication), #18111 ([feat] Upload from URL), and #13597 (Votre dossier de données et vos fichiers sont probablement accessibles depuis internet. Le fichier .htaccess ne fonctionne pas. Nous vous recommandons vivement de configurer votre serveur web de façon à ce que ce dossier de données ne soit plus accessible, ou bien de le déplacer à l'extérieur de la racine du serveur web. ).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants