The feature is implemented – you may want to look for “Restrict project naming” in your Jenkins (mange Jenkins – configure system).
Or is there something that you are missing in the current implementation? On Thursday, 17 January 2013 13:25:48 UTC, lakshmi reddy wrote: > > Hi Daniel, > > I would like to implement the naming standards for our projects. Can you > please provide me access to the github repo. > > Can you also help me in step-by-step process to implement those? > > Would really appreciate your kind help > > Thanks, > B Lakshmireddy > > Le mercredi 29 février 2012 09:48:18 UTC, Daniel PETISME a écrit : >> >> I've created the following JIRA to gather the information >> https://issues.jenkins-ci.org/browse/JENKINS-12928 >> >> Cheers >> >> Daniel >> >> >> Le jeudi 23 février 2012 14:16:17 UTC+1, Daniel PETISME a écrit : >>> >>> 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 >>> >>
