Skip to content

[CI] Jest through moon#259075

Merged
delanni merged 7 commits intoelastic:mainfrom
delanni:jest-through-moon-1
Mar 28, 2026
Merged

[CI] Jest through moon#259075
delanni merged 7 commits intoelastic:mainfrom
delanni:jest-through-moon-1

Conversation

@delanni
Copy link
Copy Markdown
Member

@delanni delanni commented Mar 23, 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.

'--no-experimental-require-module',
'$workspaceRoot/scripts/jest',
'--config',
`$projectRoot/${jestConfigName}`,
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.

we've been encoding the details to where the config can be found as arguments to the task.
I've realized we can do this instead by adding an entry to fileGroups, then refer that in any required arguments.

@delanni delanni changed the title [CI] Jest through moon - part 1 [CI] Jest through moon Mar 23, 2026
@delanni delanni added release_note:skip Skip the PR/issue when compiling release notes backport:all-open Backport to all branches that could still receive a release labels Mar 23, 2026
@delanni delanni added the ops:break-pending-prs Add before merge to record merge commit as a broke zone (outdates pending PRs) label Mar 23, 2026
@delanni
Copy link
Copy Markdown
Member Author

delanni commented Mar 23, 2026

I'll only move this to ready-for-review after the changes are accepted by @elastic/kibana-operations , so that the regenerated configs by CI will not make reviewing impossible :)

@delanni delanni force-pushed the jest-through-moon-1 branch from 955d3b4 to 5271082 Compare March 25, 2026 10:33
Copy link
Copy Markdown
Contributor

@TamerlanG TamerlanG left a comment

Choose a reason for hiding this comment

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

lgtm, tried it locally and works

@delanni delanni marked this pull request as ready for review March 25, 2026 14:47
@delanni delanni requested a review from a team as a code owner March 25, 2026 14:47
@delanni delanni force-pushed the jest-through-moon-1 branch from 4c2e84c to 661302c Compare March 27, 2026 13:50
@delanni delanni requested a review from a team as a code owner March 27, 2026 14:40
@delanni delanni force-pushed the jest-through-moon-1 branch from c1f8d9d to f06a197 Compare March 28, 2026 08:27
@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

@delanni
Copy link
Copy Markdown
Member Author

delanni commented Mar 28, 2026

Admin-merging because it's pending on an irrelevant file for review, keeping an eye on the builds

@delanni delanni merged commit 2bee636 into elastic:main Mar 28, 2026
19 checks passed
@kibanamachine
Copy link
Copy Markdown
Contributor

Starting backport for target branches: 8.19, 9.2, 9.3

https://github.com/elastic/kibana/actions/runs/23683131894

@kibanamachine
Copy link
Copy Markdown
Contributor

💔 All backports failed

Status Branch Result
8.19 Backport failed because of merge conflicts
9.2 Backport failed because of merge conflicts
9.3 Backport failed because of merge conflicts

You might need to backport the following PRs to 9.3:
- Console tutorial date based badge (#253505)

Manual backport

To create the backport manually run:

node scripts/backport --pr 259075

Questions ?

Please refer to the Backport tool documentation

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.
@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Mar 30, 2026
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 259075 locally
cc: @delanni

2 similar comments
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 259075 locally
cc: @delanni

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 259075 locally
cc: @delanni

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.
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 259075 locally
cc: @delanni

2 similar comments
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 259075 locally
cc: @delanni

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 259075 locally
cc: @delanni

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 259075 locally
cc: @delanni

tylersmalley pushed a commit that referenced this pull request Apr 8, 2026
## Summary
Manual backport of #259075

Update the config generator:

f575874

668ec4a

Then regenerate the moon configs - adds 900+ file updates, it's easier
to review the commits
tylersmalley pushed a commit that referenced this pull request Apr 8, 2026
## Summary
Manual backport of #259075

Update the config generator:
bc7b9c4
77b0dda

Then regenerate the moon configs - adds 900+ file updates, it's easier
to review the commits
delanni added a commit that referenced this pull request Apr 8, 2026
## Summary
Manual backport of #259075

Update the config generator:
3d8e7cc
0c0fdc4

Then regenerate the moon configs - adds 900+ file updates, it's easier
to review the commits
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 259075 locally
cc: @delanni

5 similar comments
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 259075 locally
cc: @delanni

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 259075 locally
cc: @delanni

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 259075 locally
cc: @delanni

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 259075 locally
cc: @delanni

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 259075 locally
cc: @delanni

@delanni delanni added backport:skip This PR does not require backporting v9.3.4 v9.2.9 v8.19.15 and removed backport missing Added to PRs automatically when the are determined to be missing a backport. backport:all-open Backport to all branches that could still receive a release labels Apr 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting ops:break-pending-prs Add before merge to record merge commit as a broke zone (outdates pending PRs) release_note:skip Skip the PR/issue when compiling release notes v8.19.15 v9.2.9 v9.3.4 v9.4.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants