-
Notifications
You must be signed in to change notification settings - Fork 4
ci: Remove Fossa add Sonarcloud #26
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
| npm test test/unit | ||
| npm test -- --coverage test/unit | ||
| - name: "Security Scan" |
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.
Do we want to make this a part of build? Do we have any other cases where we want to do security scan without build?
Maybe we should make it depend on build in case it's required for scan?
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.
SonarCloud unit test coverage requires build in order to be calculated so it would always require build. Now, the opposite question is also valid, does build require sonarcloud to run all the time? Looking through the other GH workflows in the repo, build is not reused. Release workflow actually does a build step, which is different from this one. I'd argue this workflow should be named "PR checks", similar to what we have in Python SDK, and left as is.
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.
Especially since it does type checking, test running and now SC the name fits better.
|
Kudos, SonarCloud Quality Gate passed! |








Fossa is no longer supported in Firebolt. We're now relying on dependabot for dependency scanning and sonarcloud for code smells.