Daniel, this is pretty much what I would need, but I think that would not be flexible enough for other use cases… I can think of possibilities where the job pattern has to match some security constraints and there like. Therefore I suggest we should add an extensions point for this. where are your sources? can you point me to your github repo? I i'll gone have a look and implement a new extension point for the core then. wdyt? regards Domi
On 26.02.2012, at 23:07, Daniel PETISME wrote: > > Hi guys, > > thanks for your answers. > > @Jacob I do the same trick, but it's not enought. I need to be more "strict" > > @domi As a Quick and Dirty try, I've made a prototype. Have a look at the > attachments. > > In the Gobal config page, I can specify a regexp-based naming convention. > > Then when I try to create a new job, if it doesn't match the pattern an > error message appears. > > In practice, I've modified the Jenkins core and war. It bothers me to > modified these core components... but I dont know how to make it in another > way. > > What do you thing about this Q&D solution? > > I would appreciate more coments/opinions to open an Enhancement Request. > > Cheers > > Daniel
