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

feature(github): cache github issues status in S3 #7697

Closed
wants to merge 1 commit into from

Conversation

fruch
Copy link
Contributor

@fruch fruch commented Jun 20, 2024

Ref: https://github.com/scylladb/qa-tasks/issues/1678

Testing

  • [ ]

PR pre-checks (self review)

  • I added the relevant backport labels
  • I didn't leave commented-out/debugging code

Reminders

  • Add New configuration option and document them (in sdcm/sct_config.py)
  • Add unit tests to cover my changes (under unit-test/ folder)
  • Update the Readme/doc folder relevant to this change (if needed)

@fruch fruch force-pushed the process_cache_issues_status branch from c48d2dd to 2743f7e Compare June 20, 2024 11:19
on:
schedule:
# Daily at 8:20 UTC
- cron: '20 8 * * *'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gh issue list doesn't use many requests (1 per 100 issues) and are resetting every hour. Maybe run it hourly?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't yet really setup it, I've trying to set it up correctly
and credentials is painful

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's copy paste from github examples...

and I think we still gonna do it daily

- name: Upload file to bucket
uses: koraykoska/s3-upload-github-action@[email protected]
env:
FILE: ./issues/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will it be publicitly available?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, still need to figure credentials, since it's not running in Jenkins.

@fruch fruch force-pushed the process_cache_issues_status branch 5 times, most recently from 8169fbe to e9a43c1 Compare June 20, 2024 12:34
@fruch fruch force-pushed the process_cache_issues_status branch from e9a43c1 to 4a158c1 Compare June 20, 2024 12:38
@fruch
Copy link
Contributor Author

fruch commented Jun 20, 2024

doing the work not on a fork

@fruch fruch closed this Jun 20, 2024
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

Successfully merging this pull request may close these issues.

2 participants