-
Notifications
You must be signed in to change notification settings - Fork 129
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
SQSCANGHA-42 Update scanner cli to v11.0
- Loading branch information
1 parent
8c8682d
commit 0c0f395
Showing
2 changed files
with
8 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
0c0f395
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.
Hey Istvan,
Pretty sure this release just killed my pipeline, not sure if this is intended but i think you did not include the keytool in the docker image:
0c0f395
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.
Same here!
0c0f395
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.
Hey Istvan,
After the update I'm also experiencing issues with the server certificate validation, I also tried using the SONAR_ROOT_CERT but them I received the same error reported by @BPouw. The workaround I found was specifying the previous version
sonarSource/[email protected]
.Below I attached some relevant information:
0c0f395
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.
Hello,
Thank you for your feedback, and I apologize for the inconvenience.
We are currently checking the logs and working on the solution; until that is released, could you please pin the version and use the v2.3.0 explicitly?
0c0f395
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.
The reason for the missing keytool is that you no longer include the JRE/JDK from the docker distribution, but instead bundle your own stripped down version with the sonar-scanner-cli.
For some reason, it was decided to remove the jre/bin/keytool from the linux-x64 delivery.
To avoid this problem in the future, I suggest that you add some kind of verification to the sonarqube-scan-action that the required commands are available in the docker image.
IIRC, this is the 2nd time in the past few months that the self-signed certificates/CA handling in the action/docker image breaks.
0c0f395
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.
Thank you for your feedback and suggestions @Torbjorn-Svensson.
We reverted the change that caused the breakdown. Also, as I mentioned above, we suggest referencing the commit hash or version tag instead of the branch for the action:
SonarSource/sonarqube-scan-action@2af7c4bea3abd8c236b5edb80998f31374896f09
SonarSource/[email protected]