[JIRA] (JENKINS-12928) Job name Enforcer
Title: Message Title Dominik Bartholdi commented on JENKINS-12928 Re: Job name Enforcer Sagayaraj David this was introduced way longer then folders even exist - please open a new feature request if you wold like this to be changed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12928) Job name Enforcer
Title: Message Title Sagayaraj David commented on JENKINS-12928 Re: Job name Enforcer Appreciate the Naming pattern for Project. But once I set this up, it is enforcing the patten for project as well as Folder; why is this to be applied for Folder? Could you please add three additional lines similar to the project? 1. Node naming, 2. Folder Naming and 3. View Naming Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12928) Job name Enforcer
[ https://issues.jenkins-ci.org/browse/JENKINS-12928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159810#comment-159810 ] domi commented on JENKINS-12928: This is now implemented: https://github.com/jenkinsci/jenkins/commit/a2d9bac03da99d739ecf7ce0be9ba793b93d2c88 I added a new ExtensionPoint: 'jenkins.model.ProjectNamingStrategy' and two implementations: - Default (no restriction, same as today) - Pattern (takes a regular expression to restrict the possible names) ...will be in 1.454 Job name Enforcer - Key: JENKINS-12928 URL: https://issues.jenkins-ci.org/browse/JENKINS-12928 Project: Jenkins Issue Type: New Feature Components: core Reporter: Daniel Petisme Fix For: current The aim of this feature is to be able to add constraints on job's name. For instance a simple use case is to be sure the jobs created follow a naming convention. This feature comes from the following thread in the jenkins-developer ML. [https://groups.google.com/forum/?hl=fr#!topic/jenkinsci-dev/rsxUpaNAe18] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12928) Job name Enforcer
[ https://issues.jenkins-ci.org/browse/JENKINS-12928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] domi resolved JENKINS-12928. Assignee: domi Resolution: Fixed Job name Enforcer - Key: JENKINS-12928 URL: https://issues.jenkins-ci.org/browse/JENKINS-12928 Project: Jenkins Issue Type: New Feature Components: core Reporter: Daniel Petisme Assignee: domi Fix For: current The aim of this feature is to be able to add constraints on job's name. For instance a simple use case is to be sure the jobs created follow a naming convention. This feature comes from the following thread in the jenkins-developer ML. [https://groups.google.com/forum/?hl=fr#!topic/jenkinsci-dev/rsxUpaNAe18] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12928) Job name Enforcer
[ https://issues.jenkins-ci.org/browse/JENKINS-12928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159679#comment-159679 ] domi commented on JENKINS-12928: I have this pretty much implemented, just need to clean things up a bit more... There will be a new extension point which allows you to not only reject job names, but also to transform these in to a new name. The thing is, that will also have to add this check to a job update - because a rename of the job must be controlled too. I will provide two implementation of this new extension: - default: does nothing, same as today - regex: does exactly what you have provided in your code I'll get back to you as soon as I'm further. Job name Enforcer - Key: JENKINS-12928 URL: https://issues.jenkins-ci.org/browse/JENKINS-12928 Project: Jenkins Issue Type: New Feature Components: core Reporter: Daniel Petisme Fix For: current The aim of this feature is to be able to add constraints on job's name. For instance a simple use case is to be sure the jobs created follow a naming convention. This feature comes from the following thread in the jenkins-developer ML. [https://groups.google.com/forum/?hl=fr#!topic/jenkinsci-dev/rsxUpaNAe18] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
