-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
🧪🚑 Pass a Codecov config to the action @ GHA #12508
🧪🚑 Pass a Codecov config to the action @ GHA #12508
Conversation
@RonnyPfannschmidt this probably doesn't need a change note and should be backported. |
The pytest-dev#11921 update broke uploading coverage of the `main` branch (or any in-repo pushes for that matter) to Codecov 4 months ago. Version 4 requires an upload token to be provided and since there was no configuration for it, the upload was failing. But the step itself was showing up as successful due to `fail_ci_if_error: true` being set. The error is visible in the console output, though. This patch flips the setting to `fail_ci_if_error: false` and sets the Codecov upload token in the config in clear text. The non-secret part allows the PRs uploads to be more stable. Co-authored-by: Ronny Pfannschmidt <opensource@ronnypfannschmidt.de>
e0f70a4
to
774d71a
Compare
@RonnyPfannschmidt this is auto-merge-ready now. |
UPD: it looks like the codecov action isn't picking up the config. Perhaps, it needs renaming. |
Let's try merging. Perhaps, it'll work once the config is in |
Not that comfortable with the token being public, but while Adding the Codecov token doesn't explicitly mention it, the web interface shows that as a possible option: so I suppose we'll be fine. |
Backport to 8.2.x: 💚 backport PR created✅ Backport PR branch: Backported as #12513 🤖 @patchback |
The #11921 update broke uploading coverage of the `main` branch (or any in-repo pushes for that matter) to Codecov 4 months ago. Version 4 requires an upload token to be provided and since there was no configuration for it, the upload was failing. But the step itself was showing up as successful due to `fail_ci_if_error: true` being set. The error is visible in the console output, though. This patch flips the setting to `fail_ci_if_error: false` and sets the Codecov upload token in the config in clear text. The non-secret part allows the PRs uploads to be more stable. Co-authored-by: Ronny Pfannschmidt <opensource@ronnypfannschmidt.de> (cherry picked from commit 9947ec3)
The #11921 update broke uploading coverage of the `main` branch (or any in-repo pushes for that matter) to Codecov 4 months ago. Version 4 requires an upload token to be provided and since there was no configuration for it, the upload was failing. But the step itself was showing up as successful due to `fail_ci_if_error: true` being set. The error is visible in the console output, though. This patch flips the setting to `fail_ci_if_error: false` and sets the Codecov upload token in the config in clear text. The non-secret part allows the PRs uploads to be more stable. Co-authored-by: Ronny Pfannschmidt <opensource@ronnypfannschmidt.de> (cherry picked from commit 9947ec3) Co-authored-by: Sviatoslav Sydorenko (Святослав Сидоренко) <wk@sydorenko.org.ua>
It's necessary since it seems that the currently used Codecov uploader doesn't read the token from config sometimes. This is a follow-up for pytest-dev#12508 which wasn't enough.
The pytest-dev#11921 update broke uploading coverage of the `main` branch (or any in-repo pushes for that matter) to Codecov 4 months ago. Version 4 requires an upload token to be provided and since there was no configuration for it, the upload was failing. But the step itself was showing up as successful due to `fail_ci_if_error: true` being set. The error is visible in the console output, though. This patch flips the setting to `fail_ci_if_error: false` and sets the Codecov upload token in the config in clear text. The non-secret part allows the PRs uploads to be more stable. Co-authored-by: Ronny Pfannschmidt <opensource@ronnypfannschmidt.de>
It's necessary since it seems that the currently used Codecov uploader doesn't read the token from config sometimes. This is a follow-up for pytest-dev#12508 which wasn't enough.
The #11921 update broke uploading coverage of the
main
branch (or any in-repo pushes for that matter) to Codecov 4 months ago. Version 4 requires an upload token to be provided and since there was no configuration for it, the upload was failing. But the step itself was showing up as successful due tofail_ci_if_error: true
being set. The error is visible in the console output, though.This patch flips the setting to
fail_ci_if_error: false
and sets the Codecov upload token in the config in clear text. The non-secret part allows the PRs uploads to be more stable.