Summary
I try to build images on Gitlab-CI with CNB. I can't chose the path from which I build the image because of this, but I would like to have a proper hierarchy in the final image.
Example :
My Gitlab-CI job use paketobuildpacks/builder:base as a base image and checkout the code in /builds/myapp (I can't chose that). I need to set CNB_APP_DIR to /builds/myapp, otherwise CNB doesn't know where is the code. But in the final image, the constructed hierarchy is also /builds/myapp and I would need it be /workspace/ for example.
From what I saw, it was possible with the PACK_APP_DIR variable introduced here #35 but it was removed after. #223 seems to talk about the exact issue i'm facing, but without pointing to some solution.
Is there any solution to decorrelate the location of the code used by the buildpacks and the location of the hierarchy in the final image ?
lifecycle version
0.16.0
platform version(s)
0.9
Summary
I try to build images on
Gitlab-CIwith CNB. I can't chose the path from which I build the image because of this, but I would like to have a proper hierarchy in the final image.Example :
My Gitlab-CI job use
paketobuildpacks/builder:baseas a base image and checkout the code in/builds/myapp(I can't chose that). I need to setCNB_APP_DIRto/builds/myapp, otherwise CNB doesn't know where is the code. But in the final image, the constructed hierarchy is also/builds/myappand I would need it be/workspace/for example.From what I saw, it was possible with the
PACK_APP_DIRvariable introduced here #35 but it was removed after. #223 seems to talk about the exact issue i'm facing, but without pointing to some solution.Is there any solution to decorrelate the location of the code used by the buildpacks and the location of the hierarchy in the final image ?
lifecycle version
0.16.0
platform version(s)
0.9