[CI] Jest through moon#253279
Closed
delanni wants to merge 44 commits intoelastic:mainfrom
Closed
Conversation
Contributor
|
🤖 Jobs for this PR can be triggered through checkboxes. 🚧
ℹ️ To trigger the CI, please tick the checkbox below 👇
|
1787454 to
1b706ef
Compare
a362dfa to
924223b
Compare
924223b to
ec28178
Compare
0326e0f to
1ff0e1a
Compare
703fdef to
de349cf
Compare
delanni
commented
Mar 12, 2026
delanni
commented
Mar 13, 2026
| ts-node .buildkite/scripts/pipelines/pull_request/pipeline.ts | ||
| pipeline_status=$? | ||
|
|
||
| if [[ $pipeline_status -ne 0 ]]; then |
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
History
|
This was referenced Mar 23, 2026
Member
Author
|
Closing in favor of: |
delanni
added a commit
that referenced
this pull request
Mar 28, 2026
## Summary Splitting: #253279 into multiple parts. Part 1: remove jest task details from individual configs. This PR refreshes the current (erroneous) jest setup, and extracts the specifics of the jest command to the task file containing the jest command. We can switch these tasks to point to a file with their fileGroups, then refer these tokens in the shared commands, this way, any local specificity is captured in a filegroup entry (once per concern) then any task can just refer to these in the shared/centralized point of describing the task. This PR will run a moon config regeneration, removing the jest tasks, so it will be a 1000+ file update. I've added a single moon file regenerated to show a preview of how the change would look.
SoniaSanzV
pushed a commit
to SoniaSanzV/kibana
that referenced
this pull request
Mar 30, 2026
## Summary Splitting: elastic#253279 into multiple parts. Part 1: remove jest task details from individual configs. This PR refreshes the current (erroneous) jest setup, and extracts the specifics of the jest command to the task file containing the jest command. We can switch these tasks to point to a file with their fileGroups, then refer these tokens in the shared commands, this way, any local specificity is captured in a filegroup entry (once per concern) then any task can just refer to these in the shared/centralized point of describing the task. This PR will run a moon config regeneration, removing the jest tasks, so it will be a 1000+ file update. I've added a single moon file regenerated to show a preview of how the change would look.
jeramysoucy
pushed a commit
to jeramysoucy/kibana
that referenced
this pull request
Apr 1, 2026
## Summary Splitting: elastic#253279 into multiple parts. Part 1: remove jest task details from individual configs. This PR refreshes the current (erroneous) jest setup, and extracts the specifics of the jest command to the task file containing the jest command. We can switch these tasks to point to a file with their fileGroups, then refer these tokens in the shared commands, this way, any local specificity is captured in a filegroup entry (once per concern) then any task can just refer to these in the shared/centralized point of describing the task. This PR will run a moon config regeneration, removing the jest tasks, so it will be a 1000+ file update. I've added a single moon file regenerated to show a preview of how the change would look.
paulinashakirova
pushed a commit
to paulinashakirova/kibana
that referenced
this pull request
Apr 2, 2026
## Summary Splitting: elastic#253279 into multiple parts. Part 1: remove jest task details from individual configs. This PR refreshes the current (erroneous) jest setup, and extracts the specifics of the jest command to the task file containing the jest command. We can switch these tasks to point to a file with their fileGroups, then refer these tokens in the shared commands, this way, any local specificity is captured in a filegroup entry (once per concern) then any task can just refer to these in the shared/centralized point of describing the task. This PR will run a moon config regeneration, removing the jest tasks, so it will be a 1000+ file update. I've added a single moon file regenerated to show a preview of how the change would look.
delanni
added a commit
that referenced
this pull request
Apr 2, 2026
## Summary Split from: #253279 - adopt affected-packages for selective jest/jest-integration - behind the label: `ci:use-selective-testing`
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Apr 2, 2026
## 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)
delanni
added a commit
to delanni/kibana
that referenced
this pull request
Apr 14, 2026
## 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
delanni
added a commit
to delanni/kibana
that referenced
this pull request
Apr 14, 2026
## 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 file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds/uses the module to find what packages were affected in the PR - then pre-filters jest configs for those contained in the affected subtree - thus only unit-testing packages and their downstream.