-
Notifications
You must be signed in to change notification settings - Fork 36
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
[CI] CodeCov no longer works after upgrade to v4 of the action #490
Comments
Failure on a PR from a fork, looks like upload succeeds but gets 500 error, no coverage report:
|
@opensearch-project/admin can you help to add a new token here? |
Looks to me like its a broader issues and only impacts the backports, because they are not from forked repos. From what I understood Tokenless uploading is still supported. https://github.com/codecov/codecov-action?tab=readme-ov-file#breaking-changes
We should try to address this to all repos and see how this can be fixed when updated to Thanks |
That's what I initially thought but the evidence in PRs shows otherwise. It says "Tokenless uploading is unsupported." What it does allow is a fork of an upstream to use the upstream's token in a PR to the upstream. This is a trivial exercise when one has access to add secrets to the repo.
This would take me about 30 seconds. |
Token has been added under |
Thanks @gaiksaya ! |
What is the bug?
#484 upgraded our codecov GitHub Action dependency from v3 to v4. One of the listed Breaking Changes is:
This results in failures in our CI workflow:
How can one reproduce the bug?
What is the expected behavior?
Code coverage, as established org-wide, see opensearch-project/opensearch-plugins#46 and related issues.
What is your host/environment?
GitHub Actions
Do you have any additional context?
The resolution instructions at the CodeCov repo indicate adding an appropriate Secret to the repo will resolve this. We would add a
token:
field under thewith:
here referencing that secret:However, individual repo maintainers do not have permissions to edit secrets, so resolving this will require EE team to add the secrets both here and org-wide.
I did experiment on my fork (which, as a fork, the docs say could have used the upstream public repo's token) with the standard-named token, but it doesn't seem to be present, so needs to be added.
CC @bbarani
The text was updated successfully, but these errors were encountered: