Ah, that's why our releases aren't showing up. But what exact part of the update center generation causes load on Jira/Confluence? It looked like the job shouldn't mess a lot with it, just request each plugin's page once.
There are lots of "com.atlassian.confluence.rpc.RemoteException: You're not allowed to view that page, or it does not exist." messages in the log for the pages that are generally publicly accessible. On Tuesday, May 27, 2014 2:41:42 AM UTC+4, R Tyler Croy wrote: > > See this ticket for more details < > https://issues.jenkins-ci.org/browse/INFRA-70> > > > I'm waiting to hear back from KK on how we can fix the update-center > generation > scripts from scraping/DoSing our JIRA instance before I re-enable the job. > > > > - R. Tyler Croy > > ------------------------------------------------------ > Code: <https://github.com/rtyler> > Chatter: <https://twitter.com/agentdero> > > % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F > ------------------------------------------------------ > -- 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]. For more options, visit https://groups.google.com/d/optout.
