Skip to content

Conversation

@sharbuz
Copy link
Contributor

@sharbuz sharbuz commented Dec 13, 2023

What is the problem this PR solves?

Backport pipeline initiation

How does this PR solve the problem?

Added the Buildkite pipeline configuration and "dummy" pipeline

Related issues

#8721

@sharbuz sharbuz self-assigned this Dec 13, 2023
@sharbuz sharbuz requested a review from a team as a code owner December 13, 2023 16:55
@elasticmachine
Copy link

elasticmachine commented Dec 13, 2023

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

Comment on lines +197 to +200
ingest-fp:
access_level: MANAGE_BUILD_AND_READ
everyone:
access_level: READ_ONLY
Copy link
Member

Choose a reason for hiding this comment

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

The idea for this pipeline is that everyone in the company can run it. But I guess we can change this later when the implementation is ready.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Exactly, this should be BUILD_AND_READ. But it could be updated at the end of the process if we want to test first ourselves.

@elasticmachine
Copy link

elasticmachine commented Dec 13, 2023

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-12-14T10:28:13.592+0000

  • Duration: 128 min 9 sec

Test stats 🧪

Test Results
Failed 0
Passed 4923
Skipped 6
Total 4929

Steps errors 4

Expand to view the steps failures

Test integration: aws
  • Took 65 min 47 sec . View more details here
  • Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage
Boot up the Elastic stack
  • Took 2 min 51 sec . View more details here
  • Description: ../../build/elastic-package stack up -d -v --version 8.11.0
Test integration: vsphere
  • Took 1 min 3 sec . View more details here
  • Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage
elastic-package report benchmark
  • Took 0 min 0 sec . View more details here
  • Description: elastic-package report benchmark --fail-on-missing=false --new="build/benchmark-results" --old="build/main/benchmark-results" --threshold=15 --report-output-path="report.md" --full=false

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@elasticmachine
Copy link

elasticmachine commented Dec 13, 2023

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 100.0% (456/456) 💚
Files 96.112% (791/823) 👍
Classes 96.112% (791/823) 👍
Methods 92.3% (7636/8273) 👎 -0.006
Lines 88.744% (178207/200810) 👍
Conditionals 100.0% (0/0) 💚

Copy link
Collaborator

@mrodm mrodm left a comment

Choose a reason for hiding this comment

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

Just needed to add the mark --- for the YAML document separation.

Comment on lines +197 to +200
ingest-fp:
access_level: MANAGE_BUILD_AND_READ
everyone:
access_level: READ_ONLY
Copy link
Collaborator

Choose a reason for hiding this comment

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

Exactly, this should be BUILD_AND_READ. But it could be updated at the end of the process if we want to test first ourselves.

Copy link
Collaborator

@mrodm mrodm left a comment

Choose a reason for hiding this comment

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

👍

@jsoriano jsoriano merged commit 6730481 into elastic:main Dec 14, 2023
@sharbuz sharbuz deleted the backport-pipeline-init branch December 14, 2023 14:48
tomsonpl added a commit that referenced this pull request Dec 9, 2025
… ECS mappings

- Apply path LIKE pattern instead of directory= to ensure shortcut metadata is populated
- Add event.* ECS fields (category, type, module, dataset)
- Add MITRE ATT&CK threat context fields (framework, tactic, technique)
- Add human-readable datetime() formatting for timestamp columns
- Fix column aliasing (authenticode_* → signature_*) for proper ECS mapping
- Remove Shellbags cross-reference for cleaner query execution
- Update coreMigrationVersion to 9.2.0
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.

4 participants