Fix metricbeat generator test to use mage test#18086
Fix metricbeat generator test to use mage test#18086blakerouse merged 4 commits intoelastic:masterfrom
Conversation
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
💚 Build SucceededExpand to view the summary
Build stats
Steps errorsExpand to view the steps failures
|
|
Got it further but it seems to be breaking on building the packaging now. With |
|
run beats-ci/package |
Maybe generators magefiles need to use |
|
run tests |
|
It looks like we are dealing with two separate failures. We merged one change that broke the generators and then while it was broken merged another change that caused a new failure. I think @jsoriano is correct, that The other failure has something to with the k8s dependencies in the go.mod / go.sum of the "new beat". The error I'm seeing looks like it's getting the wrong version of k8s.io/apimachinery? |
518ffb6 to
f2af20f
Compare
f2af20f to
3a109a5
Compare
make unit-test* Use mage unit-test. * Should be make. * Update mage test. * Add PackageKibanaDashboardsFromBuildDir. (cherry picked from commit 9e7321a)
What does this PR do?
Updates the generated custom metricbeat to use
mage testinstead ofmake unit.Why is it important?
So the generator tests pass.
Checklist
[ ] 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.asciidocorCHANGELOG-developer.next.asciidoc.