We released azure-commons 0.2.2.1 yesterday, however, after a whole day, we still cannot see it in Update Center or in the plugin landing page https://plugins.jenkins.io/azure-commons
I know there's some outage early today that the repo.jenkins-ci.org was out of service. I'm not sure if that's the cause.
Do we need to wait some more time for the system to pick up the new release automatically, as how it worked in the past experience, or do we need to release a new patch version to forcibly trigger the update after the issue of the repository site?
On Wednesday, December 27, 2017 at 7:57:27 PM UTC+8, Daniel Beck wrote:
> I'm not sure if that's the cause.
It is. Just wait a bit -- your plugin should appear in update sites once we're back.