In the issue https://github.com/elastic/beats/pull/17391 and looking at the Jenkinsfile I've found out that we are missing a few important platform targets to test, here an incomplete list.
I think we have to audit all x-pack jobs at least.
I've added test for the agent in https://github.com/elastic/beats/pull/17445
I created a spreadsheet with all of the test targets that I think we need (haven't looked at the generators yet).
https://docs.google.com/spreadsheets/d/1-m2-JlxeG_lmnvdL3UBQ7_BHhee_VL9J_EBM75SttLs
To make sure all of the mage targets in the listed exist I created: https://github.com/elastic/beats/pull/17773
I have prepared a table with the stages that we have now, and the ones that we may be missing: https://docs.google.com/spreadsheets/d/1cns4lri45WpYkl13Qeqk3ZyCuHv-ZTpEugxKpxV_ng0
@jsoriano I think I need a legend/key for the table.
y - we have it now?
- - not applicable / doesn't exist ?
馃敶 (red) - missing?
馃挌 (green) - synonymous with y
@jsoriano I think I need a legend/key for the table.
y- we have it now?
-- not applicable / doesn't exist ?
red_circle (red) - missing?
green_heart (green) - synonymous withy
Legend added to the spreadsheet.
Regarding this particular issue, since I'm working on the 2.0 Pipeline implementation, I created a script to generate the table with what beats are enabled in the CI and what build/stages are enabled for each, please see below:
https://github.com/elastic/beats/pull/20104#build-stages
__NOTE__: the above-mentioned PR is still in progress, but wanted to clarify that we can create what we run in the CI in a markdown table.