Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement "Keep-Alive" for Daniel Ridge bot so that Docker image will be updated #6266

Open
13 tasks
Tracked by #5644
roslynwythe opened this issue Feb 8, 2024 · 23 comments · May be fixed by danielridgebot/check-ghpages-versions#21
Open
13 tasks
Tracked by #5644

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Feb 8, 2024

Overview

We need to implement a "Keepalive Workflow" for the Daniel Ridge bot so that it performs its function of checking the dependencies for the Docker image and when necessary, updating the Dockerfile, which triggers the process of updating our Docker hub image.

Details

Action Items

  • Clone the repository check-ghpages-versions.
  • Read and understand Daniel Ridge Bot Ops Wiki, Keep Alive Workflow and
    How To Use section of the Keep-Alive Workflow documentation
    • Note the section "Moving the keepalive workflow into its own distinct job is strongly recommended for better security" and understand the sample code
  • Incorporate the Keepalive Workflow GitHub action so that it will prevent workflows from being disabled due to inactivity in the repo
  • For testing, modify both the workflows so that they create the issue in your repository
    • .github/workflows/check-ruby-version.yml
    • .github/workflows/check-gh-pages-version.yml
  • create a PAT in your repository, then a secret called test_Daniel_Ridge_PAT and modify each workflow to use that secret in place of GH_TOKEN: ${{ secrets.Daniel_Ridge_PAT }}
  • As described in How To Use section of the Keep-Alive Workflow documentation, workflow permissions must be set. Go to repository settings, Click on Actions > General. Update the "Workflow permissions" to "Read and write permissions". Click on save.
  • On the wiki page https://github.com/hackforla/ops/wiki/@danielridgebot-Ops-Wiki, add a top-level bullet under check-gh-pages-version,yml explaning the addition of the KeepAlive Workflow action
  • Test by running .github/workflows/check-gh-pages-version.yml and verify that the appropriate issues were created
  • Restore the original secret in both workflows
  • Create a PR in https://github.com/danielridgebot/check-ghpages-versions. Put this issue in "Questions/In Review" and apply the label "ready for dev lead".

Resources/Instructions

check-gh-pages-version.yml
Keep Alive Workflow
How To Use section of the Keep-Alive Workflow documentation

@roslynwythe roslynwythe added role: back end/devOps Tasks for back-end developers Complexity: Medium Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing size: 1pt Can be done in 4-6 hours Draft Issue is still in the process of being created Feature: Docker role missing Complexity: Missing labels Feb 8, 2024
@github-actions github-actions bot removed Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing role missing Complexity: Missing labels Feb 8, 2024
@roslynwythe roslynwythe added ready for product and removed Draft Issue is still in the process of being created labels Feb 8, 2024
@roslynwythe

This comment was marked as outdated.

@ExperimentsInHonesty

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed ready for product labels Feb 11, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the time sensitive Needs to be worked on by a particular timeframe label Feb 13, 2024
@roslynwythe roslynwythe added Ready for Prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Feb 25, 2024
@ExperimentsInHonesty

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Ready for Prioritization labels Feb 25, 2024
@ExperimentsInHonesty

This comment was marked as outdated.

@roslynwythe

This comment was marked as outdated.

@roslynwythe roslynwythe added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization labels Jun 14, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this to Questions / In Review in P: HfLA Website: Project Board Jun 23, 2024
@t-will-gillis t-will-gillis moved this from Questions / In Review to New Issue Approval in P: HfLA Website: Project Board Jun 30, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from New Issue Approval to Questions / In Review in P: HfLA Website: Project Board Jul 2, 2024
@ExperimentsInHonesty

This comment was marked as outdated.

This comment was marked as outdated.

@github-actions github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Aug 2, 2024

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty removed the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Sep 24, 2024
@ExperimentsInHonesty

This comment was marked as outdated.

@roslynwythe roslynwythe removed time sensitive Needs to be worked on by a particular timeframe ready for dev lead Issues that tech leads or merge team members need to follow up on labels Nov 3, 2024
@roslynwythe

This comment was marked as outdated.

@ExperimentsInHonesty

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty moved this from Questions / In Review to New Issue Approval in P: HfLA Website: Project Board Nov 5, 2024
@ExperimentsInHonesty ExperimentsInHonesty added Draft Issue is still in the process of being created and removed Added to dev/pm agenda labels Nov 5, 2024
@HackforLABot

This comment was marked as outdated.

@roslynwythe roslynwythe added Ready for Prioritization and removed Draft Issue is still in the process of being created labels Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: New Issue Approval
Development

Successfully merging a pull request may close this issue.

6 participants