Disabling or renaming default Java offline buildpack makes Healthwatch CF CLI tests to fail

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

Customers may decide to either rename of disable the default buildpack (java_buildpack_offline) in favour of a custom one, with different name. This will cause to start receiving alerts from Healthwatch where
Healthwatch TAS CLI tests are failing.

This happens because Healthwatch deploys a Java app to test the push where the java_buildpack_offline is spacified with -b flag. 
 

cf push healthwatch-sli-test-app -p /var/vcap/packages/pas-sli-exporter-payload/pas-sli-exporter-payload.jar -u process --no-start -m 1G -k 256M -b java_buildpack_offline

This cause the test to fail because java_buildpack_offline is not available any more, since it has a different name.

Environment

Product Version: 2.12

Resolution

The solution would be to rename the custom buildpacks to "java_buildpack_offline" so the test finds a buildpack to deploy the test app. 

 

R&D is working in a feature so java builpack name can be specified in Healthwatch Tile in future versions.