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

[OS] Run jobs on GitHub actions #59

Closed
2 of 3 tasks
ryscheng opened this issue May 16, 2023 · 3 comments
Closed
2 of 3 tasks

[OS] Run jobs on GitHub actions #59

ryscheng opened this issue May 16, 2023 · 3 comments
Assignees

Comments

@ryscheng
Copy link
Member

ryscheng commented May 16, 2023

Describe the feature you'd like to request

Would love for our data fetching scripts to run on the regular in GitHub Actions CI.

Describe the solution you'd like

This includes:

  • Refactoring our scripts to be idempotent
  • Setting up a standard environment (either in Docker or actions config)
  • Setting up a new GitHub actions environment for secrets

Describe alternatives you've considered

N/A

@ryscheng
Copy link
Member Author

hypercerts-org/hypercerts#741

This PR sets up os-observer to run in GitHub actions via a CLI interface.
Currently manually triggered.

@ryscheng ryscheng changed the title [OS] Scheduled jobs on GitHub actions [OS] Run jobs on GitHub actions May 28, 2023
@ryscheng
Copy link
Member Author

hypercerts-org/hypercerts#737

This adds os-observer to the monorepo and turbo builds

@ryscheng
Copy link
Member Author

I'm going to close this out, since we can trigger os-observer manually from GitHub actions here:
https://github.com/hypercerts-org/hypercerts/actions/workflows/os-observer.yml

See here for an example run:
https://github.com/hypercerts-org/hypercerts/actions/runs/5106660306/jobs/9178986925

It'd be a trivial change at this point to make it run on a schedule
https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#schedule

I'm going to close out this issue and open this issue for the remaining script rewriting work:
#56

@ryscheng ryscheng transferred this issue from hypercerts-org/hypercerts Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants