See https://git-wip-us.apache.org/repos/asf?p=calcite-site.git vs https://github.com/apache/calcite-site/commits/master
I've triggered a resync using https://gitbox.apache.org/setup/resync.cgi and will ping infra if the issue persists.
Francis On 31/03/2022 4:06 pm, Francis Chuang wrote:
Hey everyone,I just pushed [1], [2] and [3] to calcite, calcite-avatica and calcite-avatica-go to implement automated website builds. As a test commit, I fixed the release announcement for Calcite 1.30.0 [4]. It was built by Github actions in run 2068981585 [5] and was deployed to calcite-site in commit 401cc9b154af584b4babb5bfd68e6fa4d4f020bd [6]. The actual website at https://calcite.apache.org/ still has not reflected the latest changes, but I think it's just a bit slow synchronizing.I have added some filters to stop code changes from being published before a release for calcite-avatica and calcite-avatica-go.See:- https://github.com/apache/calcite-avatica/blob/master/.github/workflows/publish-non-release-website-updates.yml#L8 - https://github.com/apache/calcite-avatica-go/blob/master/.github/workflows/publish-website.yml#L10 - https://github.com/apache/calcite-avatica-go/blob/master/.github/workflows/publish-website.yml#L26 - https://github.com/apache/calcite-avatica/blob/master/site/add-avatica-go-docs.sh#L22Please test this out when updating the website in the future and report any issues or edge-cases.Francis[1] https://github.com/apache/calcite/commit/970ba276e78f15e65382b6d881519a65d1a60d45[2] https://github.com/apache/calcite-avatica/commit/b9aa1fb97189c082598daa72d997451878a25cbf[3] https://github.com/apache/calcite-avatica-go/commit/00df39b540bcb009a6b80de37fe16dfcc4d02a07[4] https://github.com/apache/calcite/commit/f43a43141d4cd1e4d4b14799e7ec820d27298512[5] https://github.com/apache/calcite/actions/runs/2068981585[6] https://github.com/apache/calcite-site/commit/401cc9b154af584b4babb5bfd68e6fa4d4f020bd
