Plugins site is behind jenkins_release tweets

[daniel-beck]

Service(s)

plugins.jenkins.io, Other

Summary

3085 has been addressed (thanks for that!) but as a side effect, it reveals a problem with the caching intervals of plugins.jenkins.io. Clicking links to the plugin site as they scroll by is confusing, as it will not have updated yet.

As an example, the newest tweet (around an hour old as I write this) links to https://plugins.jenkins.io/artifact-repository-parameter/?utm_source=rss2twitter&utm_medium=twitter, which still claims the latest release is 2.0.0 from two weeks ago, more than 1.5 hrs after its release.

While I've long thought this behavior of the plugin site wasn't ideal (mostly for my unusual use cases), realistically is has fairly low impact on users: Jenkins checks for updates once a day, and I doubt many users continually update to the very latest releases, so I would guess they're fairly unlikely to arrive on outdated plugin pages and being able to notice.

But the tweet -> plugin site connection revealing a discrepancy is more of a problem IMO.

While the optimal solution would probably be to shorten caching/speed up update intervals on the plugin site, as an alternative, we could look into artificially delaying tweets.

Alternatively, if we have logging from @jenkins_release links and/or the plugin site URLs's query parameters, perhaps nobody is actually clicking on anything?

(Obviously not super high priority :) )

Reproduction steps

No response

[dduportal]

Given the direction Twitter/X is going, is this issue still worth the effort @daniel-beck ? I'm genuinely asking but I don't mind working on it :)

[daniel-beck]

No opinion. While the bot exists, this issue exists. You could help the demise of X-Twitter along by deleting the bot.