-
Notifications
You must be signed in to change notification settings - Fork 158
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
[CI] Monorepo diff plugin for integration tests #4906
Conversation
This pull request does not have a backport label. Could you fix it @pazone? 🙏
NOTE: |
/test |
/test |
1 similar comment
/test |
/test |
/test |
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.
@cmacknz @blakerouse @rdner Could you please take a look at the list of watched paths? |
|
* [CI] Monorepo diff plugin for integration tests * [CI] Monorepo diff plugin for integration tests * [CI] Monorepo diff plugin for integration tests * [CI] Monorepo diff plugin for integration tests * Debug * Debug * Debug * Debug * Debug * Debug * Debug * Debug * Debug * Debug * Cleanup * Cleanup * added missing watch paths (cherry picked from commit fd8d1ee) # Conflicts: # .buildkite/pull-requests.json
#4922) * [CI] Monorepo diff plugin for integration tests (#4906) * [CI] Monorepo diff plugin for integration tests * [CI] Monorepo diff plugin for integration tests * [CI] Monorepo diff plugin for integration tests * [CI] Monorepo diff plugin for integration tests * Debug * Debug * Debug * Debug * Debug * Debug * Debug * Debug * Debug * Debug * Cleanup * Cleanup * added missing watch paths (cherry picked from commit fd8d1ee) # Conflicts: # .buildkite/pull-requests.json * Fixed conflicts * Fixed conflicts --------- Co-authored-by: Pavel Zorin <pavel.zorin@elastic.co>
What does this PR do?
Use monorepo diff plugin to run integration tests for pull requests and branches.
The plugin specifies a list of watched paths for pull requests. If a PR modifies files under a path from the list - integration tests will be executed.
The main pipeline triggers
elastic-agent-extended-testing
if all conditions are met:skip-it
label is not setWhen a PR is merged to main or a release branch the integration tests will be triggered in any case
That's how it looks now:
Why is it important?
The previous approach wasn't flexible enough and the separate integration testing pipeline didn't allow to run integration tests conditionally due to required checks limitation.
Important: if we add
skip-it
label - the PR will be mergeable without running integration tests.Checklist
./changelog/fragments
using the changelog toolAdditional checks
GITHUB_PULL_REQUEST_DRAFT
env variable to the build)/test
comment must trigger unit and integration tests also for draft PRsskip-it
must not trigger integration testsDisruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself