This repository has been archived by the owner on Aug 3, 2019. It is now read-only.
[JENKINS-57884] Remove the need for using client api auth class #6
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.
As suggested by @justinharringa here, I have removed the credentials matchers using auth models defined in the
client.api
package as we do not have the overhead of dealing with api methods inside our plugin. So all authentication details can be fetched as follows:Token:
credentials.getToken().getPlainText()
where credentials is of typePersonalAccessToken
Username/Password
credentials.getUsername()
/credentials.getPassword().getPlainText()
where credentials is a genericStandardUsernamePasswordCredentials
I am keeping the models as it is for now, maybe it will be required in future else remove it.