bk(crosscompile): packaging already runs in the CI

[v1v]

Proposed commit message

Packaging occurs at a later stage, so let's avoid cross-compilation and the issues associated with qemu.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• 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 in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

[botelastic]

This pull request doesn't have a Team:<team> label.

[pkoutsovasilis]

Just to echo the same message, I also support the idea of not cross-compiling (using emulation) in our CI since we have proper packaging on the right arch runners. @cmacknz @rdner wdyt?

PS: I believe that also the libbeat crosscompile CI step should be removed

[cmacknz]

Just to echo the same message, I also support the idea of not cross-compiling (using emulation) in our CI since we have proper packaging on the right arch runners. @cmacknz @rdner wdyt?

Agreed, no need to use emulation to cross compile in CI.

PS: I believe that also the libbeat crosscompile CI step should be removed

Also agreed.

It looks like these targets go all the way back to the Jenkinsfile, perhaps they predate the existing packaging step or something. That they aren't used consistently in all the Beats also makes me suspect they aren't critical. There is no equivalent target for Filebeat for example, and that isn't causing any problems.

[v1v]

PS: I believe that also the libbeat crosscompile CI step should be removed

Also agreed.

Done, see caf8e5a (#43406)