-
Notifications
You must be signed in to change notification settings - Fork 522
backport pipeline initiation #8727
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
Conversation
🚀 Benchmarks reportTo see the full report comment with |
| ingest-fp: | ||
| access_level: MANAGE_BUILD_AND_READ | ||
| everyone: | ||
| access_level: READ_ONLY |
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.
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.
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.
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.
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Steps errors
Expand to view the steps failures
|
🌐 Coverage report
|
mrodm
left a comment
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.
Just needed to add the mark --- for the YAML document separation.
| ingest-fp: | ||
| access_level: MANAGE_BUILD_AND_READ | ||
| everyone: | ||
| access_level: READ_ONLY |
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.
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.
mrodm
left a comment
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.
👍
… 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
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