JENKINS-60897 - worth expanding into a JEP?

[Chris Kilding]

I'm currently working out the details of JENKINS-60897, an enhancement to enable the folders plugin to provide an access control layer over any credentials provider. This would affect several components (all credential providers, credentials API, CasC, folders plugin, maybe more). It may also be relevant to other access control features Jenkins has. Therefore it might be worth expanding into a JEP.

Thoughts?

[Oleg Nenashev]

With the current scope of Affected components JEP would be definitely great

[Matt Sicker]

Agreed there. I'd be interested in that JEP.

> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5758c026-29d1-4339-bb37-b5d5cb8507ca%40googlegroups.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

[Chris Kilding]

I've started work on the JEP at https://github.com/jenkinsci/jep/pull/266 . It's super early stage and there's obviously a lot of work to do on it.

At this point in time it would be good to get a proper JEP number so that it has a stable identifier, which will assist in talking about it. I assumed 401 for the sake of argument (next available number) but that's not necessarily right. How would I get one?

Chris

> https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4oyp_rBxfVOi8EgjB%2B1%2BsV9NqiutJr8D%2BkuGfz13gc_z-g%40mail.gmail.com.
>