[JIRA] (JENKINS-57920) [FUTURE] Restrict user from naming a gitlab server configuration with already existing
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57920 [FUTURE] Restrict user from naming a gitlab server configuration with already existing Change By: Parichay Barpanda Sprint: GSoC 2019. Coding Phase 1 , GSoC 2019. Coding Phase 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199892.156002464.464.1562133960685%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57920) [FUTURE] Restrict user from naming a gitlab server configuration with already existing
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57920 [FUTURE] Restrict user from naming a gitlab server configuration with already existing Change By: Oleg Nenashev Sprint: GSoC 2019. Coding Phase 1 , GSoC 2019. Coding Phase 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199892.156002464.14117.1562049963931%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57920) [FUTURE] Restrict user from naming a gitlab server configuration with already existing
Title: Message Title 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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199892.156002464.26168.1560366240062%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57920) [FUTURE] Restrict user from naming a gitlab server configuration with already existing
Title: Message Title 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
