-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Use next gen codecov uploader #18443
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
Conversation
Does anyone of us use the codecov report? Maybe we should remove it instead? Cc: @go-gitea/owners |
It will not work after we move to gitea.com and I have sent email to codecov to ask them to support Gitea but they rejected that time. |
Codecov Report
@@ Coverage Diff @@
## main #18443 +/- ##
==========================================
+ Coverage 46.03% 46.27% +0.23%
==========================================
Files 840 842 +2
Lines 92856 121156 +28300
==========================================
+ Hits 42746 56062 +13316
- Misses 43323 58290 +14967
- Partials 6787 6804 +17
Continue to review full report at Codecov.
|
I would say with switching to gitea.com - we should switch to a self-hosted code coverage explorer ... there exist some but i did not test them |
But he recommend https://github.com/codecov/uploader ? |
yes https://github.com/woodpecker-ci/plugin-codecov is exact that just a wrapper to be a plugin for drone/woodpecker |
Why even have a external service like this? For example with jest, one can just do a text-only output of the coverage report, which works offline as well as directly in the CI. I think it's better to not depend on an external service.
What's the plan here? I think it's better to stay on GH for the overall project health. |
The first big stage is Gitea hosted Gitea. |
https://alternativeto.net/software/codecov-io/?platform=self-hosted but it does not have diagrams ... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think codecov could still be useful - but equally I don't particularly use the reports.
I'm gonna approve this because if we don't do this this drone step will fail and break all of our CI in 2 days time.
However, I would equally consider approving a PR that removed it.
We'll need backports of this or the removal PRs too. So we need to get a decision in in the next 2 days. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 to what zeripath said. I don't use this, but would prefer our builds don't break. Let's discuss future options for either removing or using a different service elsewhere
|
🚀 |
PS: we dont need to remove it in release branches -> because it get skiped: when:
branch:
- main
event:
- push
- pull_request |
…) (#18741) Backport #18708 Backport #18475 Backport #18443 The CI currently downloads all go modules in each pipeline step because go modules reside outside the project directory. Fix this by introducing a volume for the `/go` directory [1] so modules are only downloaded once per pipeline using a new `deps-backend` make target. For completeness, I also included new `deps` and `deps-frontend` targets and the frontend one is also triggered explicitly on CI where needed. [1] https://docs.drone.io/pipeline/kubernetes/examples/language/golang/#dependencies * Also backports #18475 and #18443 so that is was able to merge cleanly. Co-authored-by: 6543 <[email protected]> Co-authored-by: techknowlogick <[email protected]>
@masstez ? |
current plugin do use https://github.com/codecov/codecov-bash witch will stop working on On February 1, 2022