On Tue, Feb 8, 2022 at 6:02 AM '[email protected]' via Jenkins Developers <[email protected]> wrote:
> we are still granting users permission to Artifactory for deployment of a > plugin that they maintain even if the plugin is using CD > > Is there any reason still to do this? > The initial stance for JEP-229 was that we would continue to grant maintainers personal push permission in case CD did not work for whatever reason. As the system matures and we grow more confident that automated deployments will work reliably and cover every scenario, we could plan to tighten up security in this way. To Daniel’s point, I guess the switch would be to not grant Artifactory permission to people in RPU for a CD-enabled repo, unless we wanted to add a new field to discriminate people who keep this permission for the time being from those who are maintainers and should have GH write permission but no more. > we should be able to do CD on [backport] branches > Yes. Needs to be better tested & documented, and there is probably room for some tools as well. https://gist.github.com/jglick/86a30894446ed38f918050c1180483e2#file-backport-sh-L12-L22 -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3_qk0Sfyq%3DH354pOJOwnU%2Bx5Fa12c5y0MbBrVzEOFf7w%40mail.gmail.com.
