-
Notifications
You must be signed in to change notification settings - Fork 96
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 #7701
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fruch
force-pushed
the
process_cache_issues_status
branch
7 times, most recently
from
June 20, 2024 21:45
440765c
to
a6ff35b
Compare
fruch
added
backport/2023.1
Need to backport to 2023.1
backport/5.4
Need backport to 5.4
backport/2024.1
Need backport to 2024.1
backport/6.0
labels
Jun 20, 2024
fruch
commented
Jun 20, 2024
fruch
commented
Jun 20, 2024
fruch
commented
Jun 20, 2024
soyacz
reviewed
Jun 21, 2024
I wonder also about if this cache could be reused by Argus. In that case we might want to also cache also issue titles. |
fruch
force-pushed
the
process_cache_issues_status
branch
from
June 23, 2024 20:18
a6ff35b
to
a8b306b
Compare
one github action that runs once a day, that caches the issues status from multiple github repositories and client code that can read those csv files and cache them locally, so SkipPerIssue can read first out of it and then fallback into doing direct github API calls Ref: scylladb/qa-tasks#1678
fruch
force-pushed
the
process_cache_issues_status
branch
from
June 24, 2024 06:10
a8b306b
to
ec52c62
Compare
soyacz
approved these changes
Jun 24, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
2 tasks
This was referenced Jun 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport/5.4
Need backport to 5.4
backport/6.0
backport/2023.1
Need to backport to 2023.1
backport/2024.1
Need backport to 2024.1
promoted-to-master
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ref: https://github.com/scylladb/qa-tasks/issues/1678
Testing
PR pre-checks (self review)
backport
labelsReminders
sdcm/sct_config.py
)unit-test/
folder)