add first attempt at page building tests for CI

[gonuke]

Add a CI workflow that builds the pages and saves them as an artifact that is a ZIP file of the full built site. That artifact can be downloaded, unpacked and served locally (python3 -m http.server) and then reviewed on a local port.

The artifact is found by clicking on the test, navigating the the test "Summary" and scrolling down.

[MicahGale]

I am used to limiting this to specific branches. However, if you aren't deploying anything I think that won't be necessary here.

[magnoxemo]

Should we also update the README.md with the new build instructions (downloading the artifact and building it locally using python)? We can keep the Docker option for folks who want to build it locally first and then open a PR.

[MicahGale]

Should we also update the README.md with the new build instructions (downloading the artifact and building it locally using python)? We can keep the Docker option for folks who want to build it locally first and then open a PR.

Not necessarily, being able to build locally is still helpful, and how it ought to be done for large updates.

[gonuke]

Should we also update the README.md with the new build instructions (downloading the artifact and building it locally using python)? We can keep the Docker option for folks who want to build it locally first and then open a PR.

Not necessarily, being able to build locally is still helpful, and how it ought to be done for large updates.

I think we should add something to the README, but leave the previous info as @MicahGale suggested

[lewisgross1296]

I'm not the most familiar with GitHub Actions, but my only thought is it would be nice to test that this works before merging, but it seems like a chicken and egg game where we can't test new PRs with this until it's merged. I think once people are happy with this, we can merge, test, and make additional PRs as needed.

Also, would be cool to have a bot that auto comments the built link like how https://github.com/moosebuild does for docs/coverage/etc.

[gonuke]

I'm not the most familiar with GitHub Actions, but my only thought is it would be nice to test that this works before merging, but it seems like a chicken and egg game where we can't test new PRs with this until it's merged. I think once people are happy with this, we can merge, test, and make additional PRs as needed.

The test that was run on this PR demonstrates it

[gonuke]

Also, would be cool to have a bot that auto comments the built link like how https://github.com/moosebuild does for docs/coverage/etc.

I am looking for a way to post a link to the artifact in the comments to make it easier to find

[lewisgross1296]

The artifact is found by clicking on the test, navigating the the test "Summary" and scrolling down.

Yeah, I'm looking at the test Summary but is the Expired where you're supposed to be able to download from?

[gonuke]

The artifact is found by clicking on the test, navigating the the test "Summary" and scrolling down.

Yeah, I'm looking at the test Summary but is the Expired where you're supposed to be able to download from?

Hmmmm.... maybe I need to set the time that it is saved

[MicahGale]

The artifact is found by clicking on the test, navigating the the test "Summary" and scrolling down.

Yeah, I'm looking at the test Summary but is the Expired where you're supposed to be able to download from?

Hmmmm.... maybe I need to set the time that it is saved

You can change this in repo settings outside the workflow. Maybe 30 days would be good? https://docs.github.com/en/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization

[MicahGale]

LGTM.