-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Adjust the position of the architecture name in Dockerlogbeat tarball #24095
Merged
Conversation
This file contains 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
Pinging @elastic/agent (Team:Agent) |
botelastic
bot
added
needs_team
Indicates that the issue/PR needs a Team:* label
and removed
needs_team
Indicates that the issue/PR needs a Team:* label
labels
Feb 18, 2021
michalpristas
approved these changes
Feb 18, 2021
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.
looks good
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
kvch
added a commit
to kvch/beats
that referenced
this pull request
Feb 18, 2021
…elastic#24095) ## What does this PR do? Previously the Dockerlogbeat tarball produced by `mage package` contained the architecture information in the wrong position. Thus, the release manager could not find the build artifact. Expected name by RM: `elastic-logging-plugin-8.0.0-SNAPSHOT-docker-plugin-amd64.tar.gz` ## Why is it important? Release job of beats is failing. (cherry picked from commit 661a557)
1 task
kvch
added a commit
to kvch/beats
that referenced
this pull request
Feb 18, 2021
…elastic#24095) ## What does this PR do? Previously the Dockerlogbeat tarball produced by `mage package` contained the architecture information in the wrong position. Thus, the release manager could not find the build artifact. Expected name by RM: `elastic-logging-plugin-8.0.0-SNAPSHOT-docker-plugin-amd64.tar.gz` ## Why is it important? Release job of beats is failing. (cherry picked from commit 661a557)
1 task
kvch
added a commit
that referenced
this pull request
Feb 18, 2021
…#24095) (#24102) ## What does this PR do? Previously the Dockerlogbeat tarball produced by `mage package` contained the architecture information in the wrong position. Thus, the release manager could not find the build artifact. Expected name by RM: `elastic-logging-plugin-8.0.0-SNAPSHOT-docker-plugin-amd64.tar.gz` ## Why is it important? Release job of beats is failing. (cherry picked from commit 661a557)
kvch
added a commit
that referenced
this pull request
Feb 18, 2021
…#24095) (#24103) ## What does this PR do? Previously the Dockerlogbeat tarball produced by `mage package` contained the architecture information in the wrong position. Thus, the release manager could not find the build artifact. Expected name by RM: `elastic-logging-plugin-8.0.0-SNAPSHOT-docker-plugin-amd64.tar.gz` ## Why is it important? Release job of beats is failing. (cherry picked from commit 661a557)
v1v
added a commit
to v1v/beats
that referenced
this pull request
Feb 23, 2021
…dows-7 * upstream/master: Remove OSS reference for kibana and elasticsearch (elastic#24164) Skip flaky TestActions on MacOSx (elastic#23966) [Filebeat][AWS] Fix vpcflow pipeline exception: Cannot invoke "Object.getClass()" because "receiver" is null (elastic#24167) [Elastic Agent] Fix docker entrypoint for elastic-agent. (elastic#24155) [PACKAGING] Push docker images with the architecture in the version (elastic#24121) [Agent] Add agent standalone manifests for system module & Pod's log collection (elastic#23938) indicator type url is in upper case (elastic#24152) [Filebeat] Document netflow internal_networks and set default (elastic#24110) [Filebeat] Adding fixes to the TI module (elastic#24133) [Enhancement] Add RotateOnStartup feature flag for file output (elastic#19347) [Ingest Manager] Fix: Successfully installed and enrolled agent running standalone (elastic#24128) Set Elastic licence type for APM server Beats update job (elastic#24122) Add logrotation section on Running Filebeat on k8s (elastic#24120) [CI] Run if manual UI (elastic#24116) [CI] enable x-pack/heartbeat in the CI (elastic#23873) chore: comment out the E2E (elastic#24109) chore: add-backport-next (elastic#24098) Adjust the position of the architecture name in Dockerlogbeat tarball (elastic#24095) Update dependencies for M1 support in System (elastic#24019)
v1v
added a commit
to v1v/beats
that referenced
this pull request
Feb 23, 2021
…-arm * upstream/master: (24 commits) Add example input autodsicover config (elastic#24157) Empty configuration options generate `<no value>` string for azure-eventhub input (elastic#24156) Remove OSS reference for kibana and elasticsearch (elastic#24164) Skip flaky TestActions on MacOSx (elastic#23966) [Filebeat][AWS] Fix vpcflow pipeline exception: Cannot invoke "Object.getClass()" because "receiver" is null (elastic#24167) [Elastic Agent] Fix docker entrypoint for elastic-agent. (elastic#24155) [PACKAGING] Push docker images with the architecture in the version (elastic#24121) [Agent] Add agent standalone manifests for system module & Pod's log collection (elastic#23938) indicator type url is in upper case (elastic#24152) [Filebeat] Document netflow internal_networks and set default (elastic#24110) [Filebeat] Adding fixes to the TI module (elastic#24133) [Enhancement] Add RotateOnStartup feature flag for file output (elastic#19347) [Ingest Manager] Fix: Successfully installed and enrolled agent running standalone (elastic#24128) Set Elastic licence type for APM server Beats update job (elastic#24122) Add logrotation section on Running Filebeat on k8s (elastic#24120) [CI] Run if manual UI (elastic#24116) [CI] enable x-pack/heartbeat in the CI (elastic#23873) chore: comment out the E2E (elastic#24109) chore: add-backport-next (elastic#24098) Adjust the position of the architecture name in Dockerlogbeat tarball (elastic#24095) ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Previously the Dockerlogbeat tarball produced by
mage package
contained the architecture information in the wrong position. Thus, the release manager could not find the build artifact.Expected name by RM:
elastic-logging-plugin-8.0.0-SNAPSHOT-docker-plugin-amd64.tar.gz
Why is it important?
Release job of beats is failing.
Checklist
- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.