On Sunday, August 14, 2016 at 1:28:50 AM UTC-4, Arvind Jayaprakash wrote: > > A world wherein the following can happen is god enough >> > > - "jenkins team" is able to offer pipelines with restricted set of > configuration points > - "development team" exercises these configs through a file in the > source code (seed.properties) but doesn't get to tinker with the pipeline > script > - a way for the "jenkins team" to ensure that the latest pipeline > libraries are being used > > There is no open-source feature for this that I know of, though you could probably cobble something together. CloudBees offers a proprietary version:
https://www.cloudbees.com/blog/new-angle-pipeline-code -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/250fade3-706e-4498-9e45-b314ef770306%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
