-
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
Fix mage package on generated beats #15140
Fix mage package on generated beats #15140
Conversation
Mage package calls some targets by name (instead of by reference), and then these targets need to be defined in the main magefile. Add mage package to the test suite so we earlier detect these issues.
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 to me. I also tested changes and they obviously fix the issue with missing targets. Thanks
I am removing the tests by now because they were problematic in OSX builds where docker is not installed, and in local builds where I found it creating files owned by root (because of running the build on docker). |
Ok, ended up keeping the tests, but only on Linux builds, tests pass now. |
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.
Thanks for fixing this! LGTM.
Mage package calls some targets by name (instead of by reference), and then these targets need to be defined in the main magefile. Add mage package to the test suite so we earlier detect these issues. (cherry picked from commit 315837b)
Mage package calls some targets by name (instead of by reference), and then these targets need to be defined in the main magefile. Add mage package to the test suite so we earlier detect these issues. (cherry picked from commit 315837b)
Mage package calls some targets by name (instead of by reference), and then these targets need to be defined in the main magefile. Add mage package to the test suite so we earlier detect these issues. (cherry picked from commit 315837b)
…elastic#15383) Mage package calls some targets by name (instead of by reference), and then these targets need to be defined in the main magefile. Add mage package to the test suite so we earlier detect these issues. (cherry picked from commit 3535491)
Mage package calls some targets by name (instead of by reference), and
then these targets need to be defined in the main magefile.
Add mage package to the test suite so we earlier detect these issues.
This is probably broken since #14162
Fix #15122