-
Notifications
You must be signed in to change notification settings - Fork 484
chore(.github/workflowsw): move main CI checks to merge queue runs
#3887
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
Conversation
acd62bd to
b742c82
Compare
BenchmarksBenchmark execution time: 2025-09-03 14:40:47 Comparing candidate commit 957c7cf in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 24 metrics, 0 unstable metrics. |
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.
Looks good, thank you!
d742705 to
849e00d
Compare
main CI checks to merge queue runsmain CI checks to merge queue runs
8635ff7 to
58b7fa2
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.
LGTM
f9521df to
bd8a68a
Compare
|
/merge |
|
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
dario.castane@datadoghq.com unqueued this merge request |
| runs-on: ${{ matrix.runs-on }} | ||
| ref: ${{ inputs.ref || github.ref }} | ||
| secrets: inherit | ||
| go-version: "1.25" # Should be the highest supported version of Go |
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.
Would be neat if that supported the stable alias?
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.
That introduces the "risk" of having red CI if a new Go release causes the pipeline to fail. I prefer to have control, in the same line of the previous point about stating explicitly configs equivalent to the defaults.
|
/merge -c |
|
View all feedbacks in Devflow UI.
|
| inputs: | ||
| ref: | ||
| description: 'System Tests ref/tag/branch' | ||
| required: true | ||
| default: main | ||
| type: string | ||
| inputs: | ||
| ref: | ||
| description: 'System Tests ref/tag/branch' | ||
| required: true | ||
| default: main | ||
| type: string |
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.
Is it just me or I think this part in indented differently ?
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.
It had extra indentation, that's why it was modified.
…e soon-to-be merged PR as they ran on it
…flakiness is more probable while testing the PR
…and Integration Tests
…le validation workflow
ba0972d to
957c7cf
Compare
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do?
Updates workflows so
mainCI checks happen during a merge queue run. Specifically it marks all workflows that run in push events tomainto run on those events on branches starting withmq-working-branch.Additionally:
pull_requesttriggers to explicitly setopened,reopened, andsynchronizeddefault states.tags-ignoreforpushtriggers to ignore all nested modules' version tags.merge_grouptriggers.synchronizedevent onpull-request-title-validation.pull-requestworkflow.main-branch-testswithpull-requests, making sure any flakiness is early detected.main-branch-testsrun only high-signalunit-integration-testswith a smaller set.system-tests.system-tests,pull-request, ormain-branch-tests.Motivation
Clarify CI usage and ensure that failing CI checks have visibility and impact. Currently we can only see if anything is wrong on
mainby looking at the CI checks for a commit in GitHub's UI.Note 1: this PR requires a small change on repository's settings to move the required checks
PR Unit and Integration Tests / test-coreandPR Unit and Integration Tests / test-contribtoPR Unit and Integration Tests.Note 2: this PR would cause that no check will run if somebody with admin privileges doesn't use the merge queue. It should be possible to avoid that by setting some kind of break glass job that must run when merging directly from the UI. Merge queue should work by skipping it.
Reviewer's Checklist
./scripts/lint.shlocally.Unsure? Have a question? Request a review!