I’m also very interested in tracking this problem. In my case, and while the existence of new versions is being picked up by checkupdates, these versions are not being built since Jan. 9, as seen by fdroidbot. Any hints to solve it would be very much appreciated
It may work, but I still don’t see the LibreTorrent (3.0) update that I published over a week ago. Also a couple of days ago 3.0.1 was published. It seems to me that it will never be build
Apps updated/merged few days ago are already available (like K-9 Mail) but apps from previous build, merged a week ago, are not available (like my app I actually watched successfully built on wiki).
It looks like my app was built on Feb. 15, but a problem was found. I released a new update straight away, which was quickly picked up by fdroidbot. Yet, the app is not being built again. As @igor-cali asked, are there any hints on how build can be triggered?
@apozas My app has just been built after a further metadata update.
Now, the previously pending and the latest and greatest version were built at the same time.
I am not sure if this was driven by the further update, or if it the build was eventually queued.
Thank you @igor-cali for the tip. I made a trivial update to the metadata file, let’s hope it works.
Also, thank you @relan for the information. I am however not sure that the problem is a delay in the the build server catching up. The fdroiddata version that is being used for building is (significantly) more recent than the last update of my app, so this shouldn’t be a problem?
There are still some builds pending. We doubled the overall build timeout (commit), so if such build server outage happens again, it’ll catch up faster.