kevingurney commented on issue #325: URL: https://github.com/apache/arrow-site/issues/325#issuecomment-1450490714
A quick status update: I've been actively working on implementing workaround 3. (run the website deployment workflow inside of an `ubuntu:latest` container) in the `mathworks/arrow-site` fork. However, getting the entire website deployment workflow to run successfully inside of an `ubuntu:latest` container has turned out to be more complicated than expected due to a variety of differences between the `ubuntu-latest` and `ubuntu:latest` environments. [I managed to get the workflow to succeed on the `mathworks/arrow-site` fork once](https://github.com/mathworks/arrow-site/actions/runs/4305544929). However, I had to change a significant portion of the workflow to get this working. Also, the use of `apt-get update` appears to be slowing the workflow down quite significantly (this might be resolvable through caching, but I have yet to get a chance to explore this). You can see the history of attempts at getting the workflow running here: https://github.com/mathworks/arrow-site/actions Two more important issues I ran into while trying to get the container approach working: 1. I had to manually create a `gh-pages` branch before running the workflow. 2. I had to manually switch the deployment branch to `gh-pages` in the settings of the `mathworks/arrow-site` repository. I suspect that 1. shouldn't be required to get the workflow running. It isn't clear to me at this point why [this code](https://github.com/mathworks/arrow-site/blob/32bf020bd93b73674147ee118be63e250d36b4a2/.github/workflows/deploy.yml#L95) was failing to create the `gh-pages` programmatically. Also, it seems like `README.md` for `arrow-site` could be improved by adding a note that 2. is required when testing on a fork. I can follow up with a PR to address this. Given the issues / tradeoffs here, it will take some more time to get this working effectively. To unblock the website deployment for other PRs, we could consider pursuing workaround 1. or 2. described in this issue as short term solutions. I'm open to whatever approach the community prefers. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
