-
Notifications
You must be signed in to change notification settings - Fork 927
Weekly Test Runs on Released Branches #2702
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
base: unstable
Are you sure you want to change the base?
Weekly Test Runs on Released Branches #2702
Conversation
0de885f
to
4622032
Compare
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.
I think we should prefer to use github workflow actions more than relying on APIs
const branches = await github.paginate(github.rest.repos.listBranches, { | ||
owner, | ||
repo, | ||
per_page: 100, | ||
}); |
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.
Why dont we use this kind of filter for branches:
branches:
- "[0-9].[0-9]"
Then we can filter which versions we want to run on
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.
This will support single digit branch numbers right like till 9.1. But as soon as we go 10 (multi digit version), it might break. I am not sure if github workflows supports regex.
.github/workflows/weekly.yml
Outdated
core.info(`Found release branches: ${releaseBranches.join(', ')}`); | ||
core.info(`Dispatching '${workflowId}' from ref '${workflowRef}'...`); |
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.
We can use the dispatch actions of workflows rather than the APIs, WDYT?
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.
We can refer to dail.yml to see how we can dispatch workflows
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.
uses: ./.github/workflows/update-valkey-hashes.yml
with:
version: ${{ needs.process-inputs.outputs.version }}
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.
Could you run it in your fork and share the run link here? Would like to visualize it.
@roshkhatri mentioned the daily runs on active PR against release branch. Do they conflict with each other or they just run in queued manner.
Signed-off-by: Sarthak Aggarwal <[email protected]>
4622032
to
8691d22
Compare
Signed-off-by: Sarthak Aggarwal <[email protected]>
8691d22
to
03c3d04
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## unstable #2702 +/- ##
============================================
- Coverage 72.57% 72.56% -0.01%
============================================
Files 128 128
Lines 71273 71278 +5
============================================
+ Hits 51724 51725 +1
- Misses 19549 19553 +4 🚀 New features to boost your workflow:
|
Signed-off-by: Sarthak Aggarwal <[email protected]>
Resolves: #2228
Currently, there are no tests running on the already released branches. We often do backport for bug fixes and CVEs in these older versions, and end up with multiple CI tests failures on these branches.
The PR adds support for running weekly tests on already released versions
>= 7.2
. The workflow will execute the "daily" test workflow for each of these branches onSunday 06:00 UTC
.The idea is to continuously monitor our released versions through weekly test runs (during the time when is lesser activity on github runners).