Hi All, I believe for 5 days are changes have not been propagated to Maven central.
This shows a job that’s stuck [1] and is preventing new jobs from running. I’m not sure if these builds are pushed to Maven central, but it’s worth looking at this and making sure it’s running. I tried terminating the blocking job but that did not seem to work. Maybe the CI server needs to be restarted? Also, our Microsoft powered Jenkins server [2] seems to be down. It could be Alex has run out of credits again. We should really take this over from him as it’s unfair that he has to pay for the CI credits from him own money. I have created an Azure subscription for this purpose (Apache funded, just like Alex’s), but have not found the time to migrate the jobs yet. If somebody can help me do that it might speed up this transition. Thoughts? Yishay [1] Royale-asjs [Jenkins] (apache.org)<https://ci-builds.apache.org/job/royale/job/Royale-asjs/> [2] apacheroyaleci2.westus2.cloudapp.azure.com<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/>
