Disable GitHub Pages publishing of dev.folio.org site
Description
Environment
Potential Workaround
Attachments
relates to
Checklist
hideTestRail: Results
Activity

Peter MurrayNovember 13, 2024 at 2:32 PM
Ah, sorry, David….got a little excited about closing issues in the FOLIO DevOps sprint. I agree…the AWS workflow has been fragile for quite some time. Let’s talk options.

David CrossleyNovember 13, 2024 at 4:54 AM
Argh, i had forgotten about this old open ticket. I see that you already pressed the button.
For a long time now the AWS-based build has not been operating well. They have stopped allowing us to build new branches. Hence a contributor cannot view a feature branch build. That was one of the benefits of the AWS-based build.
Until recently the "gh-pages" build was operating to build and publish to folio-org.github.io site.
We had tried many times to disable that, to no avail, e.g. see the pull/381 that lead to this ticket.
Then in early October 2024 the "gh-pages" build started failing. Its technology was very outdated. I did research and found that the way forward is to use a GitHub Actions Workflow instead. That was implemented via FOLIO-4085 at workflows/jekyll.yml
The Workflow-based build has been operating well and is very fast (much faster than the AWS-based build). It is also easier to maintain, especially regarding the Ruby version to be used.
I have been intending to talk with you Peter, about discontinuing the AWS-based build and configuring the "GitHub Pages" build to use the "dev.folio.org" domain. I will raise a separate ticket for that.
Today i did a merge to mainline. That ran the automated Jekyll Workflow and restored the GitHub Pages settings.

David CrossleyNovember 12, 2024 at 3:32 PM
Wait please.

Peter MurrayNovember 12, 2024 at 1:57 PM
Current state of the GitHub Pages settings for folio-org.github.io:
Going to click that “Unpublish site” menu choice.

David CrossleyMay 2, 2019 at 4:55 AM
Our website sources are an "Organization Pages" site at folio-org/folio-org.github.io
The documentation for creating a Pages site, explains that the naming scheme "<orgname>.github.io" is what makes it happen.
The documention for unpublishing a Pages site, says to remove its "master" branch to disable the Pages build. That is drastic, and still leaves that confusing repository name.
I wonder if instead we can just rename the repository (e.g. dev-website).
Details
Assignee
Peter MurrayPeter MurrayReporter
David CrossleyDavid CrossleyLabels
Priority
P3Sprint
NoneDevelopment Team
FOLIO DevOpsTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee

Reporter

For a long time now, we have been building and publishing the dev website under our own control via AWS. This works very nicely.
We need to disable the old "GitHub Pages" build, which also still happens automatically upon a change to the master branch.