-
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
Add functionbeat to the build process #8639
Conversation
Are you going to rename beatless in the build process in a follow-up PR? |
@kvch yes in a follow-up PR once the big one is merged. |
I will fix the make check 😢 |
e08029a
to
f226be3
Compare
@tsg rebase + make check fixed, this make it a simple self contains commit to be applied to the feature branch. |
f5e2105
to
5d8e79d
Compare
following changes: Use a custom packages.yml to only build some of the artifact. Each distribution also include a linux binary to be run on AWS lambda Some refactoring is done in the mage.go file to allow to specify a specs file more easily. Make sure that beatless is added to build/distributions/beatless
5d8e79d
to
250f36c
Compare
I think there is a small problems with make check, I've looked at the license and it should be correct. |
Found the issue, using make update at the root generate a fields.go with the wrong header but header is fine when you generate it inside the beatless directory. |
Fix the docs build issue. |
Can you print a listing of the final artifacts, so we can check they are complete? |
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.
Did some quick testing and seems fine, and the packaging commit looks sane. I think this is good.
Then the macOs one for example:
|
I will merge this |
* This add beatless/functionbeat to the build processes and do the following changes: Use a custom packages.yml to only build some of the artifact. Each distribution also include a linux binary to be run on AWS lambda Some refactoring is done in the mage.go file to allow to specify a specs file more easily. Make sure that beatless is added to build/distributions/beatless * fix the issue with license on the fields.go * Adding minimal docs to satisfy DTD requirements and not fail the build
* This add beatless/functionbeat to the build processes and do the following changes: Use a custom packages.yml to only build some of the artifact. Each distribution also include a linux binary to be run on AWS lambda Some refactoring is done in the mage.go file to allow to specify a specs file more easily. Make sure that beatless is added to build/distributions/beatless * fix the issue with license on the fields.go * Adding minimal docs to satisfy DTD requirements and not fail the build
* This add beatless/functionbeat to the build processes and do the following changes: Use a custom packages.yml to only build some of the artifact. Each distribution also include a linux binary to be run on AWS lambda Some refactoring is done in the mage.go file to allow to specify a specs file more easily. Make sure that beatless is added to build/distributions/beatless * fix the issue with license on the fields.go * Adding minimal docs to satisfy DTD requirements and not fail the build
This add beatless/functionbeat to the build processes and do the
following changes:
specs file more easily.
Notes
Depends on #8485, interesting commit is e08029a