zhoufenqin

Hi @Flanker32, Does this bug fixed? the current release version is v1.36.0, but the issued still open

The route cause may be like this: 1. Enable build cache will create a PVC when triggering a build 2. Build pod will create a PV if the PV does...

@matthewmcnew, as we discuss in [pivotaltracker](https://www.pivotaltracker.com/story/show/182833089), it's not easy for us to update the default storage class because other features may use the `default` storage class, and not only my...

@matthewmcnew @tylerphelan can I know which kpack version will release this feature?

+1, do you have the ETA for the feature? We need to use this feature to support our works.

I also meet the same problem, after some investigation, it was because the node had some problem, and I change a node for my pod then it solved, just share...

Great, thanks @dmikusa , I think it's different and the buildpack won't be put into runtime image /layers. I think it's a general feature, some other features may also request...

Hi @dmikusa, I just want to test `watchexec` so I use a `Procfile` and package a jar file to check if I change the jar file, whether the `watchexec` can...

> 1. I think you want this -> https://buildpacks.io/docs/app-developer-guide/run-an-app/#default-process-type-with-additional-arguments. That will let you add arguments to the default process which should be your application. > 2. You could include a...

Thanks @dmikusa > Do you know if there is a way to tell GraalVM to write the heap dump to a specific location? From [GraalVM dev ](https://www.graalvm.org/dev/reference-manual/native-image/guides/create-heap-dump/) build, I see...