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