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

remove codecov from ci #933

Merged
merged 2 commits into from
Apr 24, 2024
Merged

remove codecov from ci #933

merged 2 commits into from
Apr 24, 2024

Conversation

laurenkrugen-navapbc
Copy link
Contributor

🎫 Ticket

n/a

🛠 Changes

removing codecov from CI, since sonarqube is doing the same thing and tokenless is hitting a github api limit.

ℹ️ Context for reviewers

Link to discussion on tokenless codecov generation and rate limiting.

✅ Acceptance Validation

n/a

🔒 Security Implications

  • This PR adds a new software dependency or dependencies.
  • This PR modifies or invalidates one or more of our security controls.
  • This PR stores or transmits data that was not stored or transmitted before.
  • This PR requires additional review of its security implications for other reasons.

If any security implications apply, add Jason Ashbaugh (GitHub username: StewGoin) as a reviewer and do not merge this PR without his approval.

name: codecov-umbrella # optional
fail_ci_if_error: true # optional (default = false)
verbose: true # optional (default = false)
- name: Archive code coverage results
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this can stay

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was thinking of removing this portion instead? https://github.com/CMSgov/bcda-app/pull/933/files#diff-e42b2b9794d0333e41c8e218ece5897ea7395746b5e07d08fb85b53e36d15043L71-L74

If we remove the codecov report generation but keep in the artifact, would it fail when it searches the path for the testcoverage.out?

Copy link
Contributor

Choose a reason for hiding this comment

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

That's what I'm thinking; it's going to look for code-coverage-report and then fail

Copy link
Contributor Author

Choose a reason for hiding this comment

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

go has built-in test coverage tools, so the file still gets generated, from what I can tell.

uses: actions/upload-artifact@v2
with:
name: code-coverage-report
path: ./test_results/latest/testcoverage.out
Copy link
Contributor

Choose a reason for hiding this comment

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

thru here

@alex-dzeda alex-dzeda merged commit 592e60e into master Apr 24, 2024
3 checks passed
@alex-dzeda alex-dzeda deleted the lauren/ci-codecov branch April 24, 2024 18:17
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