[JIRA] (JENKINS-57753) Doesn't display connection established configuration is reloaded

28 views
Skip to first unread message

parichay.barpanda@gmail.com (JIRA)

unread,
May 29, 2019, 4:39:02 PM5/29/19
to jenkinsc...@googlegroups.com
Parichay Barpanda created an issue
 
Jenkins / Bug JENKINS-57753
Doesn't display connection established configuration is reloaded
Issue Type: Bug Bug
Assignee: Parichay Barpanda
Components: gitlab-branch-source-plugin
Created: 2019-05-29 20:38
Labels: gsoc-2019
Priority: Minor Minor
Reporter: Parichay Barpanda

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.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

parichay.barpanda@gmail.com (JIRA)

unread,
May 30, 2019, 3:35:02 AM5/30/19
to jenkinsc...@googlegroups.com

parichay.barpanda@gmail.com (JIRA)

unread,
May 30, 2019, 3:35:02 AM5/30/19
to jenkinsc...@googlegroups.com
Parichay Barpanda updated an issue
 
Change By: Parichay Barpanda
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.

parichay.barpanda@gmail.com (JIRA)

unread,
May 30, 2019, 3:36:01 AM5/30/19
to jenkinsc...@googlegroups.com
Parichay Barpanda updated an issue
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.

parichay.barpanda@gmail.com (JIRA)

unread,
May 30, 2019, 7:28:02 AM5/30/19
to jenkinsc...@googlegroups.com
Parichay Barpanda started work on Bug JENKINS-57753
 
Change By: Parichay Barpanda
Status: Open In Progress

parichay.barpanda@gmail.com (JIRA)

unread,
May 30, 2019, 7:30:02 AM5/30/19
to jenkinsc...@googlegroups.com
Parichay Barpanda resolved as Fixed
 

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.

Change By: Parichay Barpanda
Status: In Progress Resolved
Resolution: Fixed
Reply all
Reply to author
Forward
0 new messages