pins sonarqube scan action version #261
Closed
Conversation
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
LumaC0
force-pushed
the
sonarqube-scan-fix
branch
9 times, most recently
from
571a81e to
6a128bc
Compare
LumaC0
force-pushed
the
sonarqube-scan-fix
branch
from
6a128bc to
d5e0842
Compare
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.
Change Log Items
Description
Sonarqube scanning hasn't worked properly for some time. It looks like the environment variables aren't being captured by the action.
This fixes the secret capture, but a new error is telling me the sonarqube server can't be reached.
Rally: