Hi, >>> I'm seeing some of the docker containers have not been built, even though >>> the imagebuilders have been available on downloads for at least a day. This >>> is causing all of ASU server's clients to fail for these targets. My test >>> case:
I meant to write a blogpost on the infrastructure but did not find the time yet. In essence there is a script on our download server which is triggered each time a rsync from the buildbot workers is complete. The script figures out if packages or firmware images were build and triggers multiple things accordingly; flush CDN cache, trigger CI to build containers, notifies the upgrade server(ASU) and even updates the downloads.o.o status page. It used to work with tags in the past but something seems to have caused some hiccups, as a results Docker containers are no longer created when tagging, I’ll investigate. This automation brings the drawback of having incomplete "Upcoming Stable Release” shown on the downloads page as well as in the firmware selector. As soon as the first tagged target is build, it will appear. If we want to improve this, I think one more manual step is required to fill the gap between tagging, building and releasing. Best, Paul
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
