Unfortunately, TAP does not list the clusterbuildpack anywhere because it doesn't end up in the build plan. Therefore, if a customer wants to determine which clusterbuildpack is being used for each build, they'd have to capture the build logs and note each buildpack listed in the logs.
Capture logs for a build:
kp build logs <image-name> [flags]
Buildpack log output:
These are the specific buildpacks that actually ran during an example build. Each of these buildpacks originates from a ClusterBuildpack that is created when TAP is installed or updated.
13 of 45 buildpacks participating
tanzu-buildpacks/ca-certificates 3.11.0
tanzu-buildpacks/bellsoft-liberica 9.17.0
tanzu-buildpacks/syft 1.46.1
tanzu-buildpacks/node-engine 4.3.19
tanzu-buildpacks/gradle 7.12.0
tanzu-buildpacks/executable-jar 6.13.1
tanzu-buildpacks/apache-tomcat 7.19.0
tanzu-buildpacks/apache-tomee 1.11.1
tanzu-buildpacks/liberty 4.2.1
tanzu-buildpacks/dist-zip 5.11.2
tanzu-buildpacks/spring-boot 5.33.0
tanzu-buildpacks/image-labels 4.10.0
paketo-buildpacks/opentelemetry 2.0.0
Inspect each clusterbuildpack to see which one contains these ids and versions. In this example, it is the java buildpack.
kubectl get clusterbuildpacks
Then, to inspect one and confirm:
kubectl describe clusterbuildpack <clusterbuildpackname>
Search for the ids: tanzu-buildpacks/bellsoft-liberica and version: 9.17.0 inside its metadata, matching your log.