I know this isn't really what you're asking for, but in my organization we don't enforce any naming conventions, but the Jenkins admin creates views for different offices and purposes, and uses either the simple regex to include jobs, or the view-jobs-filter plugin, and then if a job creator wants their job to show up in the right view, they have to follow conventions. You can replace the "All" view also, so if someone creates a job that doesn't follow conventions, that job wouldn't show up in any view.
On Thu, Feb 23, 2012 at 7:16 AM, Daniel PETISME <[email protected]> wrote: > Hi guys, > > I want to know you have rules concerning the job's names? > I do and currently I don't have any tool to "force" the users to follow the > conventions. > I've the maven-enforcer plugin in mind which check if you have specify the > versions of all your dependencies for instance. > > After a (very) quick research, I didn't see any Extension or equivalent > which allows me to specify any regexp-based naming convention. > So, these modifications should be done in the core of Jenkins. > > How do you handle this use case? > > Thank you for your answers. > > Cheers > > Daniel
