Test plugin compatibility across supported SonarQube versions#2
Open
ThomasPerkins1123 wants to merge 2 commits into
Open
Test plugin compatibility across supported SonarQube versions#2ThomasPerkins1123 wants to merge 2 commits into
ThomasPerkins1123 wants to merge 2 commits into
Conversation
…ssword to a generated user token so analysis works on newer SonarQube versions that reject password-based auth.
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



What
Adds automated compatibility testing across the range of SonarQube versions
the plugin claims to support in the Marketplace properties file, so those
version ranges are backed by real end-to-end evidence rather than assumption.
Changes
configurable via
-Dsonarqube.image=<tag>(or theSONARQUBE_IMAGEenvvar),
defaulting to
9.9-community. Previously the image was hardcoded.compatibility-matrixjob runs theintegration test against the oldest tested version and both ends of the
supported Community Build range (
9.9,25.1,26.7), and raisesvm.max_map_countso newer SonarQube's Elasticsearch can start.generated user token instead of username/password, which newer SonarQube
versions reject. The token is passed via both
sonar.tokenandsonar.loginfor compatibility across the full version range.
daemons.