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

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.

---
Originally reported by baymac, imported from: [FUTURE] Restrict user from naming a gitlab server configuration with already existing

• assignee: baymac
  
• status: Open
  
• priority: Trivial
  
• component(s): gitlab-branch-source-plugin
  
• label(s): gsoc-2019
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 20251216-182730
  

Raw content of original issue

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.