[ 
https://issues.jenkins-ci.org/browse/JENKINS-13524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161830#comment-161830
 ] 

SCM/JIRA link daemon commented on JENKINS-13524:
------------------------------------------------

Code changed in jenkins
User: Seiji Sogabe
Path:
 changelog.html
 core/src/main/java/jenkins/model/ProjectNamingStrategy.java
 core/src/main/resources/jenkins/model/Messages.properties
 core/src/main/resources/jenkins/model/Messages_ja.properties
 
core/src/main/resources/jenkins/model/ProjectNamingStrategy/PatternProjectNamingStrategy/config.groovy
http://jenkins-ci.org/commit/jenkins/5587d13f58b14bffa9f77f7433358e14add9bcfa
Log:
  [FIXED JENKINS-13524] Validate project naming regex immediately





                
> Validate project naming regex immediately
> -----------------------------------------
>
>                 Key: JENKINS-13524
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13524
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: core
>            Reporter: Ben Golding
>            Assignee: sogabe
>            Priority: Minor
>
> Manage Jenkins --> Restrict project naming --> Strategy: Pattern --> Name 
> Pattern: <your regex>
> When trying to save the configuration, the regex should be checked for 
> correctness (e.g. matching parens)
> Alternatively this could even be done in real time on the configuration page.
> [Workaround: any regex errors will appear - and need to be fixed immediately 
> - when you try to configure/create a job]

--
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

        

Reply via email to