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

Update release guide and update cron-job-unit-tests to run on PRs to release branches #17713

Merged
merged 2 commits into from
Feb 11, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion .github/workflows/cron-job-unit-tests.yml
Original file line number Diff line number Diff line change
Expand Up @@ -17,11 +17,15 @@ name: "Cron Job Unit Tests"
on:
schedule: # Runs by default on master branch
- cron: '0 3 * * 6' # Runs every Saturday at 03:00 AM UTC
pull_request:
branches:
- '[0-9]+.[0-9]+.[0-9]+' # release branches
- '[0-9]+.[0-9]+.[0-9]+-[A-Za-z0-9]+' # release branches

jobs:
run-unit-tests:
name: "unit tests"
if: (github.event_name == 'schedule' && github.repository == 'apache/druid')
if: github.repository == 'apache/druid'
strategy:
fail-fast: false
matrix:
Expand Down
2 changes: 2 additions & 0 deletions distribution/asf-release-process-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -128,6 +128,8 @@ To check the CI status on a release branch, you can go to the commits page e.g.
a green ✔ in the commit description. If the commit has a failed build, please click on red ✕ icon in the commit description to go to travis build job and investigate.
You can restart a failed build via travis if it is flaky.

The release manager should also keep an eye-out for `Cron Job Unit Tests` failures: https://github.com/apache/druid/actions/workflows/cron-job-unit-tests.yml. If there are failures, we need to fix them before creating an RC.

Once all issues and PRs that are still tagged with the release milestone have been merged, closed, or removed from the milestone and CI on branch is green, the next step is to put together a release candidate.

## Initial setup to create a release candidate
Expand Down
Loading