Skip to content

[CI] Jest through moon#253279

Closed
delanni wants to merge 44 commits intoelastic:mainfrom
delanni:jest-through-moon
Closed

[CI] Jest through moon#253279
delanni wants to merge 44 commits intoelastic:mainfrom
delanni:jest-through-moon

Conversation

@delanni
Copy link
Copy Markdown
Member

@delanni delanni commented Feb 16, 2026

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.

@delanni delanni changed the title Jest through moon [CI] Jest through moon Feb 16, 2026
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Feb 16, 2026

🤖 Jobs for this PR can be triggered through checkboxes. 🚧

ℹ️ To trigger the CI, please tick the checkbox below 👇

  • Click to trigger kibana-pull-request for this PR!
  • Click to trigger kibana-deploy-project-from-pr for this PR!
  • Click to trigger kibana-deploy-cloud-from-pr for this PR!
  • Click to trigger kibana-entity-store-performance-from-pr for this PR!
  • Click to trigger kibana-storybooks-from-pr for this PR!

@delanni delanni force-pushed the jest-through-moon branch 2 times, most recently from a362dfa to 924223b Compare February 16, 2026 17:19
Comment thread .buildkite/pipeline-utils/affected-packages/index.ts
Comment thread .buildkite/scripts/pipelines/pull_request/pipeline.sh Outdated
ts-node .buildkite/scripts/pipelines/pull_request/pipeline.ts
pipeline_status=$?

if [[ $pipeline_status -ne 0 ]]; then
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is already in main

@delanni delanni linked an issue Mar 19, 2026 that may be closed by this pull request
@elasticmachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #69 / Cloud Security Posture - Group 2 Test adding Cloud Security Posture Integrations CSPM GCP CIS_GCP Organization Add Agent FLyout - Post Installation Google Cloud Shell modal pops up after user clicks on Save button when adding integration, when there are Project ID or Organization ID provided, it should use that value
  • [job] [logs] FTR Configs #52 / Ingest pipelines app Ingest Pipelines Pipelines list Pipelines tree Doesn't display the structure tree in the details flyout if the pipeline has no Pipeline processors
  • [job] [logs] FTR Configs #49 / Serverless Observability - Deployment-agnostic API integration tests SLO Health Scan "after each" hook for "returns existing scan when recent scan exists within 1h"

Metrics [docs]

✅ unchanged

History

@delanni
Copy link
Copy Markdown
Member Author

delanni commented Mar 23, 2026

@delanni delanni closed this Mar 23, 2026
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

implement jest tasks within Moon

4 participants