Among the following, my current favourite is "feathre testbed".
== Feature & Capability Focus ==
* linux-experimental-features / linux-experimental
Directly states that the job enables experimental features. This
is clear, standard industry terminology, and avoids any ambiguity
about the Linux distribution itself.
* linux-feature-testbed
Positions the job as a testbed specifically for experimental
features, which aligns perfectly with its testing nature.
* linux-exotic-features
Keeps the "exotic" keyword you proposed but qualifies it with
"features", immediately removing the risk of sounding like an
exotic Linux distribution.
== Build & Configuration Focus ==
* linux-nondefault / linux-nonstandard
A build that departs from the standard, out-of-the-box
configuration.
* linux-extra-knobs
Uses Git-centric terminology. Since you customize build-time
configuration knobs to enable these experimental features, this is
highly descriptive and intuitive for developers.
* linux-super-tweaked / linux-highly-tweaked
Emphasizes that the build variables have been heavily customized.
* linux-custom-vars
A direct, no-nonsense replacement for 'linux-TEST-vars' that
clarifies that the variables are custom/customized rather than
just "test" variables.
== Testing & Robustness Focus ==
* linux-stress-features
Implies that we are stretching the capabilities of the build by
turning on non-standard configurations.
* linux-edge-cases
Focuses on the goal of the job: testing edge cases enabled by
experimental configuration variables.
* linux-all-features
If the experimental variables essentially turn on all optional
features, this is a very clean and positive name.
k