Hey Everyone, In a recent PR, we got to talking about adding github releases info to the wiki, but was mentioned its probably better to add it to plugins.jenkins.io instead (Totally agree, plus i have more skills in this area).
But I'm a little conflicted about solutions before I start doing any development I thought I could get some feedback. Idea 1) Pure javascript solution - Make the browser access github apis as anonymous (ex https://api.github.com/repos/jenkinsci/blueocean-plugin/releases) and output the content directly from the front end. Some Advantages: * No need to check every plugin to see if they are using github releases, just the one currently being rendered. * Simple straightforward change, only frontend code Some Downsides: * Could hit the anonymous per ip rate limits and things could break * May not work with the Server side rendering (probably would want to skip it to avoid slamming github anyways) 2) Update the backend api to fetch the result. Some Advantages: * As we do with all the other plugin data * cached so wouldn't need each user to hit github Some Downsides: * Would have to grab data for every plugin * So many moving parts, server, elastic search, plugin data job. * Rate limit for the actual server, not spread across all users * Less gavin skillset Probably for 2, since its all repos we manage, we could do an webhook for release being created, and only update on that condition, but I'm still unsure about that. So what says you all, good/bad/other ideas? Gavin -- 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/CAG%3D_DuuwHd-vLUnJB75m5X%2B2n557_oQWHU6pHTza-hz3g1n7PQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
