Creating capability from external plugin may result in NullPointerExceptions when searching for capabilities

Summary

Some custom capabilities and capabilities from third party plugins can cause a NullPointerException when searching for capabilities at Plan Configuration >> Job >> Requirements.

Steps to Reproduce

1. Add a custom capability of type Executable at Bamboo Administration >> Overview >> Server capabilities with the label system.git.executable2
2. Job Configuration >> Requirements >> Search >> enter a character > NullPointerException

Or

1. Install the Bamboozled ruby plugin
2. Add a capability of type Xvfb Run at Bamboo Administration >> Overview >> Server capabilities
3. Job Configuration >> Requirements >> Search >> enter a character > NullPointerException

Expected Results

Search works.

Actual Results

The below exception is thrown in the atlassian-bamboo.log file:

[BambooRuntimeExceptionMapper] Unexpected error from REST call
java.lang.NullPointerException
        at com.atlassian.bamboo.plugins.rest.resource.CapabilityResource.lambda$getAllCapabilitiesOnServer$1(CapabilityResource.java:76)
        at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174)
        at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
        at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
        at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
        at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
        at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
        at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
        at com.atlassian.bamboo.plugins.rest.resource.CapabilityResource.getAllCapabilitiesOnServer(CapabilityResource.java:81)

Workaround

It can be very difficult to understand which capability is causing it. Best to raise a support ticket so Atlassian can assist with the troubleshooting: http://support.atlassian.com

If you know which capability it is:

• Remove the custom capability triggering the issue.

If you know which plugin is causing it:

• Disable the plugin with the capability at Bamboo Administration >> Overview >> Manage Add-ons