Skip to content

[ci] Remove plugin build#197125

Merged
jbudz merged 8 commits intoelastic:mainfrom
jbudz:rm-platform-plugins-build
Nov 6, 2024
Merged

[ci] Remove plugin build#197125
jbudz merged 8 commits intoelastic:mainfrom
jbudz:rm-platform-plugins-build

Conversation

@jbudz
Copy link
Contributor

@jbudz jbudz commented Oct 21, 2024

The platform plugin builds were used when functional tests were, at times, run from source.
This is mostly no longer a requirement. There are two remaining cypress scripts that I updated to use the build instead.

With the time saved I'm dropping the number of vCPUs from 16 to 8. These are mostly underutilized by this step, with the exception of the distribution plugin build.

jbudz added 2 commits October 21, 2024 14:06
The platform plugin builds were used at a time when functional tests
were, at times, run from source.

This is mostly no longer a requirement. There are two remaining cypress
scripts that I updated to use the build instead.
@jbudz
Copy link
Contributor Author

jbudz commented Oct 21, 2024

buildkite test this

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

@jbudz
Copy link
Contributor Author

jbudz commented Nov 1, 2024

buildkite test this

@jbudz
Copy link
Contributor Author

jbudz commented Nov 1, 2024

buildkite test this

@jbudz
Copy link
Contributor Author

jbudz commented Nov 1, 2024

buildkite test this

@jbudz
Copy link
Contributor Author

jbudz commented Nov 1, 2024

Build testing the defend workflows changes: https://buildkite.com/elastic/kibana-pull-request/builds/247852

@jbudz jbudz added Team:Operations Kibana-Operations Team release_note:skip Skip the PR/issue when compiling release notes backport:prev-minor labels Nov 1, 2024
@jbudz
Copy link
Contributor Author

jbudz commented Nov 4, 2024

buildkite test this

@jbudz jbudz requested a review from a team November 4, 2024 23:23
@jbudz jbudz marked this pull request as ready for review November 4, 2024 23:23
@jbudz jbudz requested a review from a team as a code owner November 4, 2024 23:23
@jbudz jbudz requested a review from a team November 4, 2024 23:23
@jbudz jbudz requested a review from a team as a code owner November 4, 2024 23:23
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@jbudz jbudz requested review from a team, pzl and szwarckonrad and removed request for a team November 4, 2024 23:23
@jbudz jbudz merged commit 6b7c5b9 into elastic:main Nov 6, 2024
@kibanamachine
Copy link
Contributor

Starting backport for target branches: 8.x

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

@jbudz
Copy link
Contributor Author

jbudz commented Nov 6, 2024

I'm going to leave the backport unresolved for a while to monitor for issues. This expectation has been built in to most of our test pipelines for years, there's a decent chance I missed something and will need to revert.

@kibanamachine
Copy link
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 197125 locally

@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Nov 7, 2024
jbudz added a commit to jbudz/kibana that referenced this pull request Nov 7, 2024
The platform plugin builds were used when functional tests were, at
times, run from source.
This is mostly no longer a requirement. There are two remaining cypress
scripts that I updated to use the build instead.

With the time saved I'm dropping the number of vCPUs from 16 to 8. These
are mostly underutilized by this step, with the exception of the
distribution plugin build.
@kibanamachine
Copy link
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

3 similar comments
@kibanamachine
Copy link
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

@kibanamachine
Copy link
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

@kibanamachine
Copy link
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

@kibanamachine
Copy link
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

6 similar comments
@kibanamachine
Copy link
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

@kibanamachine
Copy link
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

@kibanamachine
Copy link
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

@kibanamachine
Copy link
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

@kibanamachine
Copy link
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

@kibanamachine
Copy link
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

jbudz added a commit that referenced this pull request Nov 25, 2024
@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Nov 25, 2024
pheyos added a commit that referenced this pull request Jan 8, 2025
…205896)

## Summary

This PR fixes the performance test pipelines by removing the bits that
rely on the plugins build.

### Details

* The plugin build has been removed with #197125. Since the performance
pipelines are running against a Kibana build (and not against sources),
they should not need the plugin build.
* The `performance-data-set-extraction` pipeline started to fail
immediately after the plugin build has been removed
* This failure went unnoticed since the `scalability-benchmarking`
pipeline continued to work by using the last uploaded artifacts from the
`performance-data-set-extraction` pipeline, which were available for
another month. Once the old artifacts were no longer available, the
`scalability-benchmarking` pipeline also started to fail.
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Jan 8, 2025
…lastic#205896)

## Summary

This PR fixes the performance test pipelines by removing the bits that
rely on the plugins build.

### Details

* The plugin build has been removed with elastic#197125. Since the performance
pipelines are running against a Kibana build (and not against sources),
they should not need the plugin build.
* The `performance-data-set-extraction` pipeline started to fail
immediately after the plugin build has been removed
* This failure went unnoticed since the `scalability-benchmarking`
pipeline continued to work by using the last uploaded artifacts from the
`performance-data-set-extraction` pipeline, which were available for
another month. Once the old artifacts were no longer available, the
`scalability-benchmarking` pipeline also started to fail.

(cherry picked from commit 9bdc995)
kibanamachine added a commit that referenced this pull request Jan 9, 2025
…nes (#205896) (#205930)

# Backport

This will backport the following commits from `main` to `8.x`:
- [Remove usage of Kibana plugins build in performance test pipelines
(#205896)](#205896)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Robert
Oskamp","email":"robert.oskamp@elastic.co"},"sourceCommit":{"committedDate":"2025-01-08T16:15:33Z","message":"Remove
usage of Kibana plugins build in performance test pipelines
(#205896)\n\n## Summary\r\n\r\nThis PR fixes the performance test
pipelines by removing the bits that\r\nrely on the plugins
build.\r\n\r\n### Details\r\n\r\n* The plugin build has been removed
with #197125. Since the performance\r\npipelines are running against a
Kibana build (and not against sources),\r\nthey should not need the
plugin build.\r\n* The `performance-data-set-extraction` pipeline
started to fail\r\nimmediately after the plugin build has been
removed\r\n* This failure went unnoticed since the
`scalability-benchmarking`\r\npipeline continued to work by using the
last uploaded artifacts from the\r\n`performance-data-set-extraction`
pipeline, which were available for\r\nanother month. Once the old
artifacts were no longer available, the\r\n`scalability-benchmarking`
pipeline also started to
fail.","sha":"9bdc995d3c6f1c19d242d411e039e1c9c5c6251f","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","v8.18.0"],"title":"Remove
usage of Kibana plugins build in performance test
pipelines","number":205896,"url":"https://github.com/elastic/kibana/pull/205896","mergeCommit":{"message":"Remove
usage of Kibana plugins build in performance test pipelines
(#205896)\n\n## Summary\r\n\r\nThis PR fixes the performance test
pipelines by removing the bits that\r\nrely on the plugins
build.\r\n\r\n### Details\r\n\r\n* The plugin build has been removed
with #197125. Since the performance\r\npipelines are running against a
Kibana build (and not against sources),\r\nthey should not need the
plugin build.\r\n* The `performance-data-set-extraction` pipeline
started to fail\r\nimmediately after the plugin build has been
removed\r\n* This failure went unnoticed since the
`scalability-benchmarking`\r\npipeline continued to work by using the
last uploaded artifacts from the\r\n`performance-data-set-extraction`
pipeline, which were available for\r\nanother month. Once the old
artifacts were no longer available, the\r\n`scalability-benchmarking`
pipeline also started to
fail.","sha":"9bdc995d3c6f1c19d242d411e039e1c9c5c6251f"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205896","number":205896,"mergeCommit":{"message":"Remove
usage of Kibana plugins build in performance test pipelines
(#205896)\n\n## Summary\r\n\r\nThis PR fixes the performance test
pipelines by removing the bits that\r\nrely on the plugins
build.\r\n\r\n### Details\r\n\r\n* The plugin build has been removed
with #197125. Since the performance\r\npipelines are running against a
Kibana build (and not against sources),\r\nthey should not need the
plugin build.\r\n* The `performance-data-set-extraction` pipeline
started to fail\r\nimmediately after the plugin build has been
removed\r\n* This failure went unnoticed since the
`scalability-benchmarking`\r\npipeline continued to work by using the
last uploaded artifacts from the\r\n`performance-data-set-extraction`
pipeline, which were available for\r\nanother month. Once the old
artifacts were no longer available, the\r\n`scalability-benchmarking`
pipeline also started to
fail.","sha":"9bdc995d3c6f1c19d242d411e039e1c9c5c6251f"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Robert Oskamp <robert.oskamp@elastic.co>
viduni94 pushed a commit to viduni94/kibana that referenced this pull request Jan 23, 2025
…lastic#205896)

## Summary

This PR fixes the performance test pipelines by removing the bits that
rely on the plugins build.

### Details

* The plugin build has been removed with elastic#197125. Since the performance
pipelines are running against a Kibana build (and not against sources),
they should not need the plugin build.
* The `performance-data-set-extraction` pipeline started to fail
immediately after the plugin build has been removed
* This failure went unnoticed since the `scalability-benchmarking`
pipeline continued to work by using the last uploaded artifacts from the
`performance-data-set-extraction` pipeline, which were available for
another month. Once the old artifacts were no longer available, the
`scalability-benchmarking` pipeline also started to fail.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release_note:skip Skip the PR/issue when compiling release notes Team:Operations Kibana-Operations Team v9.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants