[KB] create `@kbn/product-doc-artifact-builder` package #193847

pgayvallet · 2024-09-24T10:48:24Z

Summary

Related #193473

Add initial implementation of the knowledge base artifact builder. This PR only introduces the builder script, it doesn't do anything about automation.

pgayvallet · 2024-10-02T08:52:08Z

/ci

pgayvallet · 2024-10-02T09:10:08Z

/ci

pgayvallet · 2024-10-02T12:08:53Z

/ci

elasticmachine · 2024-10-02T13:27:54Z

Pinging @elastic/appex-ai-infra (Team:AI Infra)

pgayvallet · 2024-10-02T13:30:19Z

src/dev/precommit_hook/casing_check_config.js

@@ -116,6 +116,7 @@ export const IGNORE_DIRECTORY_GLOBS = [
  'src/babel-*',
  'packages/*',
  'packages/core/*/*',
+  'x-pack/packages/ai-infra/*',


@elastic/kibana-operations the ai-infra packages will live in that folder, and I kinda like my package folders to follow their names (e.g ai-infra/kb-artifact-builder instead of ai-infra/kb_artifact_builder), so I took the liberty to add that pattern.

Please tell me if you'd prefer me to just go with underscores.

No issues with it

pgayvallet · 2024-10-02T13:38:20Z

@elasticmachine merge upstream

jbudz · 2024-10-02T14:00:48Z

We're CODEOWNERS on one file here, but I don't see any other reviewers. Would it help it review the entire PR?

jbudz

src/dev/precommit_hook/casing_check_config.js

pgayvallet

self-review

pgayvallet · 2024-10-02T15:10:42Z

x-pack/packages/ai-infra/kb-artifact-builder/src/build_artifacts.ts

+  // log.info('Checking connectivity against clusters');
+  // await checkConnectivity({ sourceClient, embeddingClient });


Don't have ping permission on the source cluster, had to disable that for now...

pgayvallet · 2024-10-02T15:12:05Z

x-pack/packages/ai-infra/kb-artifact-builder/src/command.ts

+    .option('stackVersion', {
+      describe: 'The stack version to generate documentation for',
+      string: true,
+      default: '8.16', // TODO: master is on 9.0 now, not sure we can default to version in package.json?


Need to figure that out at some point. version will be passed by the CI when we have this automated, so maybe using the version from the package is fine (but atm we have 0 docs for 9.0, so...)

pgayvallet · 2024-10-02T15:13:47Z

x-pack/packages/ai-infra/kb-artifact-builder/src/tasks/create_chunk_files.ts

+  const searchRes = await client.search({
+    index,
+    size: 10000,
+    query: {
+      bool: {
+        must: [{ term: { product_name: productName } }],
+      },


Should use PIT instead of size: 10000 search, but we don't have products with more than 5k documents atm, and memory usage is fine given the resources we will running the task with

Should we add a check to assert this, until we update this to use PIT?

Yeah would make sense to fail in that case rather than silently ignoring. Will do in extract_documentation as the task is done first.

pgayvallet · 2024-10-02T15:14:49Z

x-pack/packages/ai-infra/kb-artifact-builder/src/tasks/extract_documentation.ts

+  const response = await client.search({
+    index,
+    size: 10000,
+    query: {


Same as previous - it's bad, but it should be okay for now.

pgayvallet · 2024-10-02T15:15:53Z

x-pack/packages/ai-infra/kb-artifact-builder/src/tasks/perform_semantic_search.ts

+export const performSemanticSearch = async ({
+  searchQuery,
+  index,
+  client,


Unused, but keeping it for now as it will be used elsewhere in a follow-up

legrego

Overall structure and flow LGTM. My comments are primarily around logging, to help our future selves debug this.

I'm sure some of the CLI options will change as we learn more (e.g. authentication mechanism), but it's too early to think about that.

x-pack/packages/ai-infra/kb-artifact-builder/src/command.ts

legrego · 2024-10-02T18:48:05Z

x-pack/packages/ai-infra/kb-artifact-builder/src/build_artifacts.ts

+}) => {
+  log.info(`Starting building artifact for product ${productName} and version ${stackVersion}`);
+
+  const targetIndex = `kb-test-${pseudoRandSuffix()}`;


Followup/non-blocking: what do you think about a more descriptive index name? Something that references any of [current date, CI agent, product name, version] would help us keep track of these indices, and perhaps help to trace issues in the event of a job failure.

Seems better yeah, and will do, even if I'm not sure of the concrete gains if we delete the index as a finally step

x-pack/packages/ai-infra/kb-artifact-builder/src/artifact/mappings.ts

legrego · 2024-10-02T18:53:01Z

x-pack/packages/ai-infra/kb-artifact-builder/src/tasks/create_chunk_files.ts

+  const searchRes = await client.search({
+    index,
+    size: 10000,
+    query: {
+      bool: {
+        must: [{ term: { product_name: productName } }],
+      },


Should we add a check to assert this, until we update this to use PIT?

x-pack/packages/ai-infra/kb-artifact-builder/src/tasks/create_chunk_files.ts

x-pack/packages/ai-infra/kb-artifact-builder/src/tasks/create_artifact.ts

legrego · 2024-10-02T19:01:58Z

x-pack/packages/ai-infra/kb-artifact-builder/src/build_artifacts.ts

+  });
+  log.info(`Extracted ${documents.length} documents from the source cluster`);
+
+  await createTargetIndex({


Is it intentional that we don't cleanup the target index once we're done with it?

No. TBH I was keeping the index because I was then using it for my semantic search tests in the POC. And in practice everything should run on a disposable cluster. But you're right, we should (and we should also do it in case of failure as cleanup). Will adapt

…ackaging-POC

pgayvallet · 2024-10-04T06:19:52Z

@legrego I implemented all the requested changes, PTAL!

To get an idea how what logging looks like, an example on a single artifact run:

<< kibana % node scripts/build_kb_artifacts.js --stack-version 8.15 --product-name Kibana
 info Starting building artifacts for version=[8.15] and products=[Kibana]
 info Ensuring ELSER is installed on the embedding cluster
 info Starting building artifact for product [Kibana] and version [8.15]
 info Starting to extract documents from source cluster
 info Finished extracting documents from source. 589 documents were extracted
 info Starting indexing process
 info Indexed 1 of 59 chunks (took 53133ms)
[...]
 info Indexed 59 of 59 chunks (took 3057ms)
 info Finished indexing process
 info Starting to create chunk files in directory [.../kibana/build/temp-kb-artifacts/Kibana]
 info Writing chunk file content-1.ndjson containing 5 docs
[...]
 info Writing chunk file content-95.ndjson containing 6 docs
 info Finished creating chunk files
 info Starting to create artifact from build folder [.../kibana/build/temp-kb-artifacts/Kibana] into target [.../kibana/build/kb-artifacts]
 info Finished creating artifact [kibana-kb-kibana-8.15.zip]
 info Deleting index kb-artifact-builder-kibana-8.15
 info Finished building artifact for product [Kibana] and version [8.15]

…ackaging-POC

kibana-ci · 2024-10-07T12:21:10Z

💛 Build succeeded, but was flaky

Buildkite Build
Commit: f842304

Failed CI Steps

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
`@kbn/product-doc-artifact-builder`	-	1	+1

Unknown metric groups

API count

id	before	after	diff
`@kbn/product-doc-artifact-builder`	-	1	+1

History

💛 Build #239452 was flaky f3c7e4e
💛 Build #239323 was flaky 81faf99
💔 Build #239205 failed e16d1a6
💛 Build #238800 was flaky beeded9
💔 Build #238667 failed 92aff03

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

kibanamachine · 2024-10-07T12:21:32Z

Starting backport for target branches: 8.x

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

kibanamachine · 2024-10-07T12:25:57Z

💔 All backports failed

Status	Branch	Result
❌	8.x	Backport failed because of merge conflicts You might need to backport the following PRs to 8.x: - [Security Solution] Fix flaky unified component test #189791 (#195093) - github-actions: undeploy observability deployments using ephemeral GH tokens (#195215) - fix: [Obs Services > Create Service Group modal][KEYBOARD]: Focus should not be auto-set on first input when modal appears (#194696) - [Console] Disable export if no content (#195178) - [ResponseOps][Alerting] Error when submit rule form when using AddFilterPopover in actions (#194600) - [Reporting] Improvements to reporting diagnostics (#191790) - [Fleet] Do not enable uninstall command link without Agents:All (#195185) - [UII] Fix skipped test by add logs otel template to index template overlaps (#194764) - [APM][ECO] Removing Entities inventory from APM (#195116) - [HTTP/OAS] Include Security Solution domain OAS to production docs (#194132)

Manual backport

To create the backport manually run:

node scripts/backport --pr 193847

Questions ?

Please refer to the Backport tool documentation

kibanamachine · 2024-10-09T12:50:48Z

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 193847 locally

kibanamachine · 2024-10-10T13:48:56Z

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 193847 locally

kibanamachine · 2024-10-11T14:49:32Z

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 193847 locally

kibanamachine · 2024-10-14T14:51:05Z

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 193847 locally

pgayvallet · 2024-10-14T20:32:58Z

💚 All backports created successfully

Status	Branch	Result
✅	8.x

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

## Summary Related elastic#193473 Add initial implementation of the knowledge base artifact builder. This PR only introduces the builder script, it doesn't do anything about automation. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit 1ab1add) # Conflicts: # .github/CODEOWNERS

… (#196206) # Backport This will backport the following commits from `main` to `8.x`: - [[KB] create `@kbn/product-doc-artifact-builder` package (#193847)](#193847)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport)

## Summary Close #193473 Close #193474 This PR utilize the documentation packages that are build via the tool introduced by #193847, allowing to install them in Kibana and expose documentation retrieval as an LLM task that AI assistants (or other consumers) can call. Users can now decide to install the Elastic documentation from the assistant's config screen, which will expose a new tool for the assistant, `retrieve_documentation` (only implemented for the o11y assistant in the current PR, shall be done for security as a follow up). For more information, please refer to the self-review. ## General architecture <img width="1118" alt="Screenshot 2024-10-17 at 09 22 32" src="https://github.com/user-attachments/assets/3df8c30a-9ccc-49ab-92ce-c204b96d6fc4"> ## What this PR does Adds two plugin: - `productDocBase`: contains all the logic related to product documentation installation, status, and search. This is meant to be a "low level" components only responsible for this specific part. - `llmTasks`: an higher level plugin that will contain various LLM tasks to be used by assistants and genAI consumers. The intent is not to have a single place to put all llm tasks, but more to have a default place where we can introduce new tasks from. (fwiw, the `nlToEsql` task will probably be moved to that plugin). - Add a `retrieve_documentation` tool registration for the o11y assistant - Add a component on the o11y assistant configuration page to install the product doc (wiring the feature to the o11y assistant was done for testing purposes mostly, any addition / changes / enhancement should be done by the owning team - either in this PR or as a follow-up) ## What is NOT included in this PR: - Wire product base feature to the security assistant (should be done by the owning team as a follow-up) - installation - utilization as tool - FTR tests: this is somewhat blocked by the same things we need to figure out for elastic/kibana-team#1271 ## Screenshots ### Installation from o11y assistant configuration page <img width="1476" alt="Screenshot 2024-10-17 at 09 41 24" src="https://github.com/user-attachments/assets/31daa585-9fb2-400a-a2d1-5917a262367a"> ### Example of output #### Without product documentation installed <img width="739" alt="Screenshot 2024-10-10 at 09 59 41" src="https://github.com/user-attachments/assets/993fb216-6c9a-433f-bf44-f6e383d20d9d"> #### With product documentation installed <img width="718" alt="Screenshot 2024-10-10 at 09 55 38" src="https://github.com/user-attachments/assets/805ea4ca-8bc9-4355-a434-0ba81f8228a9"> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Alex Szabo <alex.szabo@elastic.co> Co-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

## Summary Close elastic#193473 Close elastic#193474 This PR utilize the documentation packages that are build via the tool introduced by elastic#193847, allowing to install them in Kibana and expose documentation retrieval as an LLM task that AI assistants (or other consumers) can call. Users can now decide to install the Elastic documentation from the assistant's config screen, which will expose a new tool for the assistant, `retrieve_documentation` (only implemented for the o11y assistant in the current PR, shall be done for security as a follow up). For more information, please refer to the self-review. ## General architecture <img width="1118" alt="Screenshot 2024-10-17 at 09 22 32" src="https://github.com/user-attachments/assets/3df8c30a-9ccc-49ab-92ce-c204b96d6fc4"> ## What this PR does Adds two plugin: - `productDocBase`: contains all the logic related to product documentation installation, status, and search. This is meant to be a "low level" components only responsible for this specific part. - `llmTasks`: an higher level plugin that will contain various LLM tasks to be used by assistants and genAI consumers. The intent is not to have a single place to put all llm tasks, but more to have a default place where we can introduce new tasks from. (fwiw, the `nlToEsql` task will probably be moved to that plugin). - Add a `retrieve_documentation` tool registration for the o11y assistant - Add a component on the o11y assistant configuration page to install the product doc (wiring the feature to the o11y assistant was done for testing purposes mostly, any addition / changes / enhancement should be done by the owning team - either in this PR or as a follow-up) ## What is NOT included in this PR: - Wire product base feature to the security assistant (should be done by the owning team as a follow-up) - installation - utilization as tool - FTR tests: this is somewhat blocked by the same things we need to figure out for elastic/kibana-team#1271 ## Screenshots ### Installation from o11y assistant configuration page <img width="1476" alt="Screenshot 2024-10-17 at 09 41 24" src="https://github.com/user-attachments/assets/31daa585-9fb2-400a-a2d1-5917a262367a"> ### Example of output #### Without product documentation installed <img width="739" alt="Screenshot 2024-10-10 at 09 59 41" src="https://github.com/user-attachments/assets/993fb216-6c9a-433f-bf44-f6e383d20d9d"> #### With product documentation installed <img width="718" alt="Screenshot 2024-10-10 at 09 55 38" src="https://github.com/user-attachments/assets/805ea4ca-8bc9-4355-a434-0ba81f8228a9"> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Alex Szabo <alex.szabo@elastic.co> Co-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit 455c781) # Conflicts: # .github/CODEOWNERS

…200754) # Backport This will backport the following commits from `main` to `8.x`: - [[LLM tasks] Add product documentation retrieval task (#194379)](#194379)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport)

## Summary Close elastic#193473 Close elastic#193474 This PR utilize the documentation packages that are build via the tool introduced by elastic#193847, allowing to install them in Kibana and expose documentation retrieval as an LLM task that AI assistants (or other consumers) can call. Users can now decide to install the Elastic documentation from the assistant's config screen, which will expose a new tool for the assistant, `retrieve_documentation` (only implemented for the o11y assistant in the current PR, shall be done for security as a follow up). For more information, please refer to the self-review. ## General architecture <img width="1118" alt="Screenshot 2024-10-17 at 09 22 32" src="https://github.com/user-attachments/assets/3df8c30a-9ccc-49ab-92ce-c204b96d6fc4"> ## What this PR does Adds two plugin: - `productDocBase`: contains all the logic related to product documentation installation, status, and search. This is meant to be a "low level" components only responsible for this specific part. - `llmTasks`: an higher level plugin that will contain various LLM tasks to be used by assistants and genAI consumers. The intent is not to have a single place to put all llm tasks, but more to have a default place where we can introduce new tasks from. (fwiw, the `nlToEsql` task will probably be moved to that plugin). - Add a `retrieve_documentation` tool registration for the o11y assistant - Add a component on the o11y assistant configuration page to install the product doc (wiring the feature to the o11y assistant was done for testing purposes mostly, any addition / changes / enhancement should be done by the owning team - either in this PR or as a follow-up) ## What is NOT included in this PR: - Wire product base feature to the security assistant (should be done by the owning team as a follow-up) - installation - utilization as tool - FTR tests: this is somewhat blocked by the same things we need to figure out for elastic/kibana-team#1271 ## Screenshots ### Installation from o11y assistant configuration page <img width="1476" alt="Screenshot 2024-10-17 at 09 41 24" src="https://github.com/user-attachments/assets/31daa585-9fb2-400a-a2d1-5917a262367a"> ### Example of output #### Without product documentation installed <img width="739" alt="Screenshot 2024-10-10 at 09 59 41" src="https://github.com/user-attachments/assets/993fb216-6c9a-433f-bf44-f6e383d20d9d"> #### With product documentation installed <img width="718" alt="Screenshot 2024-10-10 at 09 55 38" src="https://github.com/user-attachments/assets/805ea4ca-8bc9-4355-a434-0ba81f8228a9"> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Alex Szabo <alex.szabo@elastic.co> Co-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

POC of documentation packaging workflow

982ffed

pgayvallet added the Team:AI Infra AppEx AI Infrastructure Team label Sep 24, 2024

pgayvallet mentioned this pull request Sep 24, 2024

[KB] Add documentation packaging workflow #193473

Closed

create package, move all the things

b0bbcb3

pgayvallet changed the title ~~KB packaging: POC of documentation extraction~~ [KB] create @kbn/kb-artifact-builder package Oct 2, 2024

kibanamachine added 2 commits October 2, 2024 09:05

[CI] Auto-commit changed files from 'node scripts/lint_packages --fix'

a03c48d

[CI] Auto-commit changed files from 'node scripts/notice'

92aff03

pgayvallet added 2 commits October 2, 2024 14:08

minor improvements

7fe189d

add folder to list of ignored casing dirs

abeda00

pgayvallet marked this pull request as ready for review October 2, 2024 13:27

pgayvallet requested a review from a team as a code owner October 2, 2024 13:27

pgayvallet commented Oct 2, 2024

View reviewed changes

pgayvallet added release_note:skip Skip the PR/issue when compiling release notes v9.0.0 backport:prev-minor Backport to (9.0) the previous minor version (i.e. one version back from main) v8.16.0 labels Oct 2, 2024

Merge branch 'main' into kbn-193473-kb-doc-packaging-POC

beeded9

pgayvallet requested a review from a team October 2, 2024 14:54

jbudz approved these changes Oct 2, 2024

View reviewed changes

pgayvallet commented Oct 2, 2024

View reviewed changes

legrego reviewed Oct 2, 2024

View reviewed changes

pgayvallet added 2 commits October 3, 2024 18:18

address review comments

e16d1a6

Merge remote-tracking branch 'upstream/main' into kbn-193473-kb-doc-p…

81faf99

…ackaging-POC

pgayvallet disabled auto-merge October 4, 2024 13:55

pgayvallet added 2 commits October 7, 2024 11:42

Merge remote-tracking branch 'upstream/main' into kbn-193473-kb-doc-p…

dce0b58

…ackaging-POC

rename to @kbn/product-doc-artifact-builder

4352d11

pgayvallet changed the title ~~[KB] create @kbn/kb-artifact-builder package~~ [KB] create @kbn/product-doc-artifact-builder package Oct 7, 2024

pgayvallet added 2 commits October 7, 2024 11:52

generated files

6986898

rename script name

3742a2e

pgayvallet enabled auto-merge (squash) October 7, 2024 09:59

kibanamachine added 2 commits October 7, 2024 10:05

[CI] Auto-commit changed files from 'node scripts/generate codeowners'

9f44031

[CI] Auto-commit changed files from 'node scripts/notice'

f842304

pgayvallet merged commit 1ab1add into elastic:main Oct 7, 2024
41 checks passed

kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Oct 9, 2024

kibanamachine mentioned this pull request Oct 11, 2024

[Search Assistant] Use scopes to modify behavior contextually #195785

Merged

pgayvallet mentioned this pull request Oct 14, 2024

[8.x] [KB] create @kbn/product-doc-artifact-builder package (#193847) #196206

Merged

pgayvallet removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Oct 14, 2024

pgayvallet mentioned this pull request Oct 17, 2024

[LLM tasks] Add product documentation retrieval task #194379

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[KB] create `@kbn/product-doc-artifact-builder` package #193847

[KB] create `@kbn/product-doc-artifact-builder` package #193847

pgayvallet commented Sep 24, 2024 •

edited by kibanamachine

Loading

pgayvallet commented Oct 2, 2024

pgayvallet commented Oct 2, 2024

pgayvallet commented Oct 2, 2024

elasticmachine commented Oct 2, 2024

pgayvallet Oct 2, 2024

jbudz Oct 2, 2024

pgayvallet commented Oct 2, 2024

jbudz commented Oct 2, 2024

jbudz left a comment

pgayvallet left a comment

pgayvallet Oct 2, 2024

pgayvallet Oct 2, 2024

pgayvallet Oct 2, 2024

legrego Oct 2, 2024

pgayvallet Oct 3, 2024

pgayvallet Oct 2, 2024

pgayvallet Oct 2, 2024

legrego left a comment

legrego Oct 2, 2024

pgayvallet Oct 3, 2024

legrego Oct 2, 2024

legrego Oct 2, 2024

pgayvallet Oct 3, 2024

pgayvallet commented Oct 4, 2024

kibana-ci commented Oct 7, 2024

API count

kibanamachine commented Oct 7, 2024

kibanamachine commented Oct 7, 2024

kibanamachine commented Oct 9, 2024

kibanamachine commented Oct 10, 2024

kibanamachine commented Oct 11, 2024

kibanamachine commented Oct 14, 2024

pgayvallet commented Oct 14, 2024

		// log.info('Checking connectivity against clusters');
		// await checkConnectivity({ sourceClient, embeddingClient });

[KB] create @kbn/product-doc-artifact-builder package #193847

[KB] create @kbn/product-doc-artifact-builder package #193847

Conversation

pgayvallet commented Sep 24, 2024 • edited by kibanamachine Loading

Summary

pgayvallet commented Oct 2, 2024

pgayvallet commented Oct 2, 2024

pgayvallet commented Oct 2, 2024

elasticmachine commented Oct 2, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pgayvallet commented Oct 2, 2024

jbudz commented Oct 2, 2024

jbudz left a comment

Choose a reason for hiding this comment

pgayvallet left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

legrego left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pgayvallet commented Oct 4, 2024

kibana-ci commented Oct 7, 2024

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

Public APIs missing comments

API count

History

kibanamachine commented Oct 7, 2024

kibanamachine commented Oct 7, 2024

💔 All backports failed

Manual backport

Questions ?

kibanamachine commented Oct 9, 2024

kibanamachine commented Oct 10, 2024

kibanamachine commented Oct 11, 2024

kibanamachine commented Oct 14, 2024

pgayvallet commented Oct 14, 2024

💚 All backports created successfully

Questions ?

[KB] create `@kbn/product-doc-artifact-builder` package #193847

[KB] create `@kbn/product-doc-artifact-builder` package #193847

pgayvallet commented Sep 24, 2024 •

edited by kibanamachine

Loading