The update center accesses confluence to get the {excerpt} stuff for the
plugin descriptions.The (as KK likes to call it NIH) CloudBees update center that we use also scrapes Confluence... but we only scrape a plugin when we have a new version of that plugin. If scraping fails we fall back to the description in the pom and don't repeat scraping again until there is a new version. We also do other "crazy" things like being able to generate the update center JSON on the fly so we can offer different content for LTS lines vs the TIP line from the same URL (which is actually a redirect to the permanent URL that has very high cache control for the specific JSON content being served) Madness I know! OTOH we have more lines of Jenkins that we have to support and consequently less load per line whereas Jenkins OSS has the mirrors which favours static content. The real issue here is that the Jenkins OSS update center does not use a database-like[1] back-end to store the data so it has to scrape *every* plugin *every* time it runs. -Stephen [1] does not actually need to be a formal database, it could be a cache file on disk for example... if the cache is missing then hammer confluence away! On 27 May 2014 08:08, domi <[email protected]> wrote: > Why would the update center access JIRA or confluence at all? > To display the data on confluence the flow is right in the other > direction, confluence connects to the update center to get the info. And > JIRA, hmm, I have no idea why JIRA would be used for anything here… > Domi > > On 27.05.2014, at 08:46, Ivan Kalinin <[email protected]> wrote: > > 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. > > > -- > 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. > -- 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.
