[JIRA] (JENKINS-57920) [FUTURE] Restrict user from naming a gitlab server configuration with already existing

parichay.barpanda@gmail.com (JIRA)

unread,

Jun 8, 2019, 4:11:02 PM6/8/19

to jenkinsc...@googlegroups.com

Parichay Barpanda created an issue

Jenkins /

JENKINS-57920

[FUTURE] Restrict user from naming a gitlab server configuration with already existing

Issue Type:	Bug
Assignee:	Parichay Barpanda
Components:	gitlab-branch-source-plugin
Created:	2019-06-08 20:10
Labels:	gsoc-2019
Priority:	Trivial
Reporter:	Parichay Barpanda

The GitLabServer configuration name should be unique. A unique is generated automatically. But if the user wishes to change the field to an existing server name, there isn't a possible method to check if the server name already exist. Need to find a hack to this. Saving this for later as user do not generally have any incentive to change the name of server.

Add Comment

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

parichay.barpanda@gmail.com (JIRA)

unread,

Jun 12, 2019, 3:04:02 PM6/12/19

to jenkinsc...@googlegroups.com

Parichay Barpanda commented on

JENKINS-57920

Re: [FUTURE] Restrict user from naming a gitlab server configuration with already existing

Presently, if a user names a gitlab server with the same name then only the oldest server with the name is persisted. No warning is shown at the runtime.