build: add ability to disable some plugins from packaging and tests 50/39150/8
authorAndrew Yourtchenko <ayourtch@gmail.com>
Tue, 26 Sep 2023 14:01:21 +0000 (16:01 +0200)
committerDamjan Marion <dmarion@0xa5.net>
Tue, 3 Oct 2023 13:23:25 +0000 (13:23 +0000)
commitbc37878ecbad0a3a24801f1ad5af04a209b4c201
treead53a00aa4a6fd49f94a10483839f4fff0a0f2d4
parent08057947f3da441d571420d4594ce1e3888516ea
build: add ability to disable some plugins from packaging and tests

When custom-packaging the VPP artifacts, it can be useful to exclude
some of the core plugins from packaging/testing, for some reasons.
A removal of a plugin(s) from the worktree needs to be tracked as
a separate change, and thus is tricky from the maintenance
point of view.

This change adds the ability to "pretend they do not exist" -
plugins which are added to the comma-separated environment
variable "VPP_EXCLUDED_PLUGINS" will not be added to the build
process and not packaged.

The tests do not have the 1:1 relationship as plugins,
so they might need to be modified separately. This change
includes some of these modifications as an example.

Type: feature
Signed-off-by: Andrew Yourtchenko <ayourtch@gmail.com>
Change-Id: Id31562d00a01ced1acbb4996a633517cbd6f09d8
build-data/packages/vpp.mk
src/plugins/CMakeLists.txt
test/Makefile
test/asf/test_quic.py
test/config.py
test/test_abf.py
test/test_acl_plugin.py
test/test_acl_plugin_l2l3.py
test/test_acl_plugin_macip.py
test/test_ikev2.py
test/test_wireguard.py