> Workarounds to JENKINS-17200 involve writing code that gets loaded early through some mechanism.
So, I assume the credentials plugin is doing this, any direction which mechanism they're using? - Bryan On Friday, September 13, 2024 at 5:15:30 PM UTC-5 db...@cloudbees.com wrote: > On Fri, Sep 13, 2024 at 11:34 PM Bryan Stopp <bryan...@gmail.com> wrote: > >> Can anyone guide me on how to get a plugin to be registered in the system >> correctly such that permissions show up in the Matrix group/item view, *on >> boot*. >> >> If i navigate to the `Manage` view, then go to the Security section, my >> permission group and individual permissions show up. However, if i navigate >> directly to the Security view they do not. >> >> I assume it has something to do with Jenkins not finding my class or its >> describable/descriptor on boot. But I'm not able to figure out what i'm >> doing wrong. >> > > Workarounds to JENKINS-17200 involve writing code that gets loaded early > through some mechanism. Extensions aren't bad, but they are only really > loaded on demand I think, depending on how you register them, and probably > what you're experiencing. You could try an @Initializer annotated method > to make Jenkins load your class earlier than it would otherwise. > -- 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-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/921407ae-f32e-4440-b0cb-f60d57b15b74n%40googlegroups.com.
