[JIRA] (JENKINS-16224) ProjectNamingStrategy/force existing: Does not prevent modifying existing job configurations

[alb...@folk.de (JIRA)]

Harald Albers created JENKINS-16224 ProjectNamingStrategy/force existing: Does not prevent modifying existing job configurations Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 29/Dec/12 5:49 PM Description: On Jenkins' main configuration, the Restrict project naming feature has a Pattern strategy with an force existing option. Checking this option should prevent users from updating an existing job configuration if the job name does not comply with the naming convention (unless they change the project name to a complying value as well). This does not work as expected for existing jobs with non-compliant job names. After saving such a job configuration, an error page is displayed ('...' does not match the job name convention pattern ...). The changes are applied, though. See https://github.com/jenkinsci/jenkins/commit/a2d9bac03da99d739ecf7ce0be9ba793b93d2c88 for a discussion with the feature's author about the meaning of the checkbox. Project: Jenkins Priority: Minor Reporter: Harald Albers

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira