-
Notifications
You must be signed in to change notification settings - Fork 42
Finish migrating build to github actions #140
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
Comments
Can I help with this issue? Would you like any other build step or build with JDK11 or newer? Did you consider to use CodeCov instead of SonarQube? |
That would be appreciated thanks @szatyinadam! |
I think it might be helpful to understand why sonar is failing before replacing it with another tool. Since March 2024 sonar works fine on the main repo https://github.com/assertj/assertj, so maybe this project here is just not properly configured in sonar? The error message is:
Maybe the branch name changed? Maybe the project was never set up at all? It should be relatively straight forward to compare the configurations of assertj and this repo in sonar, but this needs to be done by a maintainer with the necessary permissions. |
You're right, @timo-a. This is definitely to be taken up within the team. Plus, it should be aligned with the outcome of assertj/assertj#3580. |
sonar is failing
The text was updated successfully, but these errors were encountered: