-
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
[DOCS] cd into correct directory before invoking mage. #17679
[DOCS] cd into correct directory before invoking mage. #17679
Conversation
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
1 similar comment
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
Pinging @elastic/integrations-services (Team:Services) |
❕ Build Aborted
Expand to view the summary
Build stats
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
💚 Build Succeeded
Expand to view the summary
Build stats
Trends 🧪❕ Flaky test reportNo test was executed to be analysed. |
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.
This fix is needed and looks correct.
jenkins run tests |
This will probably need to be merged against master for CI to be happy. Is @bestpath-gb still around? |
@fearful-symmetry I am! Is there anything I can do to help with this? |
@bestpath-gb can you merge against the upstream master? This branch is (I assume) very out of date. |
6a7d989
to
8f6a4d2
Compare
@fearful-symmetry I've rebased on latest upstream master. Let me know if there's anything else you need. |
jenkins run tests |
Ping @fearful-symmetry |
@bestpath-gb sorry, one last thing, can you add a changelog entry to |
This pull request is now in conflicts. Could you fix it? 🙏
|
e8df82a
to
35ae081
Compare
@fearful-symmetry Changelog entry added. |
jenkins run tests |
* upstream/master: (308 commits) [winlogbeat] Add support for sysmon v13 events 24 and 25 (elastic#24945) mergify: add backport label (elastic#25050) Add pod.ip in k8s metadata (elastic#25037) [elastic-agent] Use fleet.url for container cmd (elastic#25026) disable TestXPackEnabled flaky test in logstash metricbeat module (elastic#25034) Leverege leader election in agent k8s manifests (elastic#25016) libbeat/publisher/pipeline: expand monitoring (elastic#24700) libbeat: fix decode_json_fields config validation (elastic#24862) Remove make docs-preview instructions (elastic#25001) [Filebeat] Fix IPtables pipeline (elastic#24928) [DOCS] cd into correct directory before invoking mage. (elastic#17679) Add -buildmode=pie for supported platform (elastic#24964) Add agent's direcotry in k8s manifest generator (elastic#24987) [mergify] assign the original author (elastic#25007) Fix AWS module flaky tests (elastic#24852) [filebeat] Use fail_on_template_error on google_workspace and okta pagination (elastic#24967) Updated config to match defaults (elastic#25004) [Filebeat] Fix hardcoded amazonaws.com endpoint (elastic#24861) Add cloud.service.name to add_cloud_metadata (elastic#24993) [Ingest Manager] Expose processes and their metrics (elastic#24788) ...
Relates #14409
The docs for creating a new beat are currently wrong as they tell you to
cd
into your github home directory before callingmage GenerateCustomBeat
. This gives the errorNo .go files marked with the mage build tag in this directory.
.This PR updates the docs so the reader will create their github home directory, then
cd
into the beats directory before running Mage.