Investigate use of Daniel Ridge bot its repo 'check-ghpages-versions'

[roslynwythe]

Overview

We need to understand the purpose and status of the Daniel Ridge bot and its repo 'check-ghpages-versions', to determine if the Website team should take responsibility for maintaining it.

Details

Daniel Ridge Bot repo 'check-ghpages-versions' is intended to automatically check the dependencies for the Docker image created from ghpages-docker, and when necessary, to update the ghphages-docker Dockerfile, build a new image and push it to Docker Hub.

Action Items

• Read DanielRidge Bot Wiki
• Determine if the workflows are still needed, and if so, check the status and effectiveness of the workflows and whether any maintenance is required.
• The possibility of a stale Dockerfile has been raised in connection with several issues including ER: New Developers with Mac processors are having problems running docker image #5644 and ER: Devs running WSL Ubuntu cannot run docker-compose up #5647. Determine if the Daniel Ridge bot could play a role in solutions to these issues.
• Record findings in a comment in this issue
• Move this issue to "Questions/In Review" and add the label "ready for dev lead"

Resources/Instructions

• DanielRidge Bot Wiki
• @danielridgebot
• check-ghpages-versions
• ghpages-docker
• ghpages-docker's README
• ghpages-docker's Wiki
• Follow the steps here, How do you update ghpages-docker, for more details on to resolve issues opened by Daniel.

[github-actions]

Hi @roychan1, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[roychan1]

i. Availability: 9am-5pm
ii. ETA: 11/27 at the earliest

[roslynwythe]

Hi @roychan1 I wanted to bring these comments to your attention: #5644 (comment) and #5644 (comment)

[github-actions]

@roychan1

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, December 4, 2023 at 11:06 PM PST.}

[roychan1]

1. Progress: I have done research on the DanielRidge Bot, ghpages-docker, check-ghpages-versions repositories.
2. Blockers: I have difficulty figuring out a solution, I will communicate with someone on slack channels.
3. Availability: I will work on it this weekend (12/9 - 12/10).
4. ETA: 4 days.

[roslynwythe]

Hi @roychan1, please advise, was the "Keep-Alive Workflow" a viable solution?

[roychan1]

Hi @roychan1, please advise, was the "Keep-Alive Workflow" a viable solution?

Hi @roslynwythe , I verified that the check-ghpages-versions workflow did pause due to inactivity for 60 days, as shown in this screenshot:

The "Keep-Alive Workflow" should be a viable solution, as it is intended for cron based triggers, like Check Github Pages Gem Version and Open New Issue on Change from the check-ghpages-versions repo.

As specified in the How To Use section of the Keep-Alive Workflow documentation, its workflow name will just needed to be specified as the last step in Check Github Pages Gem Version and Open New Issue on Change workflow from check-ghpages-versions, and read/ write permissions has to be enabled on the check-ghpages-versions repo.

I believe the workflow is still needed because I verified that the version of the GitHub page ruby gem has fallen out of date. github-pages-gem.txt shows version 227 (newest version detected, not necessarily updated), while Official GitHub Pages Versions shows version 228.

The check-ghpages-versions repo's GitHub actions should have opened an issue in hackforla/ops notifying about version update, and when version in the dockerfile is updated, ghpages-docker repo's GitHub actions would rebuild the image and push it to DockerHub. The Dockerfile was stale most likely because no issues were opened to notify about version updates due to the stopping of the bot, and consequently the Docker image was not rebuilt and pushed to DockerHub. Fixing of the bot should prevent a stale dockerfile moving forward.

I have not tested the "Keep-Alive Workflow" myself so I cannot say that it functions as intended. Should I test it as part of this issue? Is there any more information I should provide or subjects I should look into for this issue? Please let me know if clarifications are needed. Thank you.

[github-actions]

@roychan1

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, December 25, 2023 at 11:06 PM PST.}

[roychan1]

1. Progress: I have included findings in this comment: Investigate use of Daniel Ridge bot its repo 'check-ghpages-versions'  #5897 (comment) and added "ready for dev lead" label. I am awaiting on a response regarding the issue.
2. Blockers: N/A
3. Availability: day time during the week of 12/31 - 1/6
4. ETA: less than a week, depending on the status of review

[roslynwythe]

@roychan1 thank you for the analysis and recommendation. This issue will be closed as completed and a new issue created for implementing the "Keep-Alive Workflow". If you are interested in writing the new issue, please message me on Slack.