Under the credentials entry, it shows a message `Cannot resolve suitable credentials with id:`. This is most probably happening because Jenkins is not sending request to GitLab Server to log in. I haven't been able to replicate this issue. Right now, when the Global configuration is loaded, it gets logged in but there is a need to show a loading symbol for the user to know that authentication with the server is being processed.
{{Cannot resolve suitable credentials with id:`. }}
This is most probably happening because Jenkins is not sending request to GitLab Server to log in. I haven't been able to replicate this issue. Right now, when the Global configuration is loaded, it gets logged in but there is a need to show a loading symbol for the user to know that authentication with the server is being processed.
This is most probably happening because Jenkins is not sending request to GitLab Server to log in. I haven't been able to replicate this issue. Right now, when the Global configuration is loaded, it gets logged in but there is a need to show a loading symbol for the user to know that authentication with the server is being processed.
Removed this issue by adding a user driven test connection button than server validation for the credential since sending requests to server takes a time thus creating a discrepancy in automatic form validation message.