-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Fleet] Use staging registry for snapshot builds #90327
Conversation
The staging registry is used in Kibana builds which are not built of the master branch or release version. This means, any build ending with `-SNAPSHOT` not the master branch will use the staging registry. Closes elastic#90131
@skh I'm struggling a bit with testing this. I tried to modify the package.json and adjust version / branch but this had many unexpected side effects as the values are also used in other places. I maybe have to cherry pick it to the 7.x branch for testing. But then I still miss |
jenkins test this |
I have tested this locally on the |
Pinging @elastic/fleet (Team:Fleet) |
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.
Approving per @skh's comment (thanks for testing Sonja!).
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
The staging registry is used in Kibana builds which are not built of the master branch or release version. This means, any build ending with `-SNAPSHOT` not the master branch will use the staging registry. Closes elastic#90131 Co-authored-by: Jen Huang <its.jenetic@gmail.com>
The staging registry is used in Kibana builds which are not built of the master branch or release version. This means, any build ending with `-SNAPSHOT` not the master branch will use the staging registry. Closes #90131 Co-authored-by: Jen Huang <its.jenetic@gmail.com> Co-authored-by: Nicolas Ruflin <spam@ruflin.com> Co-authored-by: Jen Huang <its.jenetic@gmail.com>
* master: (99 commits) [Fleet] Use Fleet Server indices in the search bar (elastic#90835) [Search Sessions] added an info flyout to session management (elastic#90559) [ILM] Revisit searchable snapshot field after new redesign (elastic#90793) [Alerting] License Errors on Alert List View (elastic#89920) RFC Improve saved object migrations algorithm (elastic#84333) [Lens] (Accessibility) Fix focus on drag and drop actions (elastic#90561) Use new shortcut links to Fleet discuss forums. (elastic#90786) Do not generate an ephemeral encryption key in production. (elastic#81511) [Fleet] Use staging registry for snapshot builds (elastic#90327) Actually deleting x-pack/tsconfig.refs.json (elastic#90898) Add deprecation warning to all Beats CM pages. (elastic#90741) skip flaky suite (elastic#90136) Revert "Revert "[Metrics UI] Add Metrics Anomaly Alert Type (elastic#89244)"" (elastic#90889) remove ref to removed tsconfig file [core.logging] Uses host timezone as default (elastic#90368) [Maps] remove maps_file_upload plugin and fold public folder into file_upload plugin (elastic#90292) Revert "[Metrics UI] Add Metrics Anomaly Alert Type (elastic#89244)" [dev-utils/ci-stats] support disabling ship errors (elastic#90851) Prefix with / (elastic#90836) [Metrics UI] Add Metrics Anomaly Alert Type (elastic#89244) ...
The staging registry is used in Kibana builds which are not built of the master branch or release version. This means, any build ending with `-SNAPSHOT` not the master branch will use the staging registry. Closes elastic#90131 Co-authored-by: Jen Huang <its.jenetic@gmail.com> # Conflicts: # x-pack/plugins/fleet/server/services/epm/registry/registry_url.ts
The staging registry is used in Kibana builds which are not built of the master branch or release version. This means, any build ending with `-SNAPSHOT` not the master branch will use the staging registry. Closes #90131 Co-authored-by: Jen Huang <its.jenetic@gmail.com> # Conflicts: # x-pack/plugins/fleet/server/services/epm/registry/registry_url.ts Co-authored-by: Nicolas Ruflin <spam@ruflin.com>
I'm pretty sure this missed the 7.11.1 build of Kibana with hash 6882b06 so I changed the label to v7.11.2 but correct me if that's wrong. |
Thanks @LeeDr. |
The Kibana repo had / has another urgent check-in coming for 7.11.1 so this will be picked up as well. |
@skh Thanks for taking this over! |
The staging registry is used in Kibana builds which are not built of the master branch or release version. This means, any build ending with
-SNAPSHOT
not the master branch will use the staging registry.Closes #90131