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

Use codecov github action #1526

Merged
merged 4 commits into from
Jul 8, 2024
Merged

Use codecov github action #1526

merged 4 commits into from
Jul 8, 2024

Conversation

EnriqueL8
Copy link
Contributor

Move to using the GitHub action as the bash script is not using the token correctly

Signed-off-by: Enrique Lacal <enrique.lacal@kaleido.io>
@EnriqueL8 EnriqueL8 requested a review from a team as a code owner June 17, 2024 16:10
Signed-off-by: Enrique Lacal <enrique.lacal@kaleido.io>
@EnriqueL8
Copy link
Contributor Author

This still doesn't work, will come back to it

Signed-off-by: Enrique Lacal <enrique.lacal@kaleido.io>
- uses: codecov/codecov-action@v4
with:
codecov_yml_path: ./codecov.yml
token: ${{ secrets.CODECOV_TOKEN }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure we've set up codecov tokens on other repos in HL previously.

I think this PR is pointing out that codecov is trying to deprecate the ability to use it without a token, and as such we might need one.

That might need a conversation with the HL team potentially, as while I believe the free tier would be fine still on codecov.io, there would need to be a user that could own the github account that is associated with the token.

Copy link
Contributor Author

@EnriqueL8 EnriqueL8 Jun 18, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The repo has a secret CODECOV_TOKEN set for the Github Action to use and the previous bash step used the token already. I have no idea who/how that token ended up in the repository, doesn't seem to be a HL thing based on not seeing anything on discord. The reality is that the token probably expired at some point in the last few months. I do wonder how we created an account against codecov and generated a token, and what email/credentials we used.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link

codecov bot commented Jul 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (81cda8c) to head (e7d5c62).
Report is 40 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #1526      +/-   ##
===========================================
+ Coverage   99.97%   100.00%   +0.02%     
===========================================
  Files         323       324       +1     
  Lines       23537     23645     +108     
===========================================
+ Hits        23530     23645     +115     
+ Misses          5         0       -5     
+ Partials        2         0       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@EnriqueL8
Copy link
Contributor Author

This now worked https://app.codecov.io/github/hyperledger/firefly/commit/582db4c8814f471d9df0b2c8df30de20f9862dc7

@ryjones changed the token inside the repo with a Hyperledger CodeCov token and gave me access to CodeCov as well

@peterbroadhurst
Copy link
Contributor

Super, thanks @EnriqueL8 and @ryjones

@peterbroadhurst peterbroadhurst merged commit a6700a8 into main Jul 8, 2024
17 checks passed
@peterbroadhurst peterbroadhurst deleted the fix_codecov branch July 8, 2024 16:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants