[9.2] [CI] Affected testing for Jest/Jest integration (#259137)#263005
[9.2] [CI] Affected testing for Jest/Jest integration (#259137)#263005delanni merged 4 commits intoelastic:9.2from
Conversation
## Summary Split from: elastic#253279 - adopt affected-packages for selective jest/jest-integration - behind the label: `ci:use-selective-testing` (cherry picked from commit 95f453a) # Conflicts: # .buildkite/pipeline-utils/ci-stats/pick_test_group_run_order.ts
|
This backport needs #263133 to be merged first |
|
@dmlemeshko - I might have mis-merged the PR. I'll clean it up manually. I noticed the feature for the filtering of empty jest tests have been missing, but it's because the parallelization PR (the one that introduced the issue in the first place) was missing. So we can skip the whole feature on these branches. I noticed this properly on the 8.19 backport, but I apparently added some unnecessary parts of the mentioned PR in this merge. |
|
@elastic/kibana-operations - please check this manual backport |
💚 Build Succeeded
Metrics [docs]
History
|
| touchedCriticalFiles, | ||
| CRITICAL_FILES_JEST_INTEGRATION_TESTS, | ||
| } from '../affected-packages'; | ||
| import { collectEnvFromLabels, expandAgentQueue } from '#pipeline-utils'; |
There was a problem hiding this comment.
shouldn't getRequiredEnv be imported from '#pipeline-utils' as well?
There was a problem hiding this comment.
Changed it now, it's a reasonable change, but it wasn't port of the original change: #259137. Let's hope it won't cause conflict on the long run
4 participants
Backport
This will backport the following commits from
mainto9.2:Questions ?
Please refer to the Backport tool documentation