fix: prevent publication with unsupported credential types #351
+9
−0
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.
fixes: #347
What changed?
Unsupported credential types are now explicitly made incompatible with the
github-checks-plugin
to avoid downstream unexpected exceptions such as the one reported here.With this change, the supported credential types are:
GitHubAppCredentials
VaultUsernamePasswordCredentialImpl
If an unsupported credential type is provided, an early
return
is done to avoid having to handle downstream exceptions caused by incompatible types. This means that all pipeline console log entries will be suppressed if the pipeline has not been configured with compatible credentials.Testing done
Procedure
As extracted from here, I have ran the following command to both build & run the test suite:
$ mvn -Penable-jacoco clean verify -B -V -ntp
A regression test was also carried out in our internal Jenkins controller to assert that previous functionality based on the above described credential types is left unaffected.
Submitter checklist