Recover x-pack Packetbeat packaging in 7.x#23538
Merged
jsoriano merged 2 commits intoelastic:7.xfrom Jan 18, 2021
Merged
Conversation
Commented-out by mistake in elastic#23142.
Contributor
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
❕ Flaky test reportNo test was executed to be analysed. |
Member
Author
|
/packaging |
Member
Author
|
/package |
v1v
approved these changes
Jan 16, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
.ci/packaging.groovyhad been done by [Packetbeat] Create x-pack magefile #21979, but reverted possibly by mistake in Cherry-pick #22076 to 7.x: Cherry-pick to 7.10: packaging backports #23142.Jenkinsfile.yml([CI] enable x-pack/packetbeat in the CI #22252) was never backported, not sure if this was intended.