[
https://issues.jenkins-ci.org/browse/JENKINS-12928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
