You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we build image using buildpacks build strategy, it works as long as command is run inside the project directory. If we run it from some different directory, build fails as pack CLI considers project directory as the one from which maven/gradle process got invoked.
Buildpacks build should detect the configured directory via the build tool. It shouldn't assume project directory as the one from which build process is initiated.
JKube should pass the project using --path flag in pack CLI arguments
Describe the bug
When we build image using buildpacks build strategy, it works as long as command is run inside the project directory. If we run it from some different directory, build fails as
pack
CLI considers project directory as the one from which maven/gradle process got invoked.To reproduce it you can clone https://github.com/rohankanojia-forks/jkube-buildpacks-poc-testing and run the following command from project base directory:
The build will fail with buildpacks complaining
No buildpack groups passed detection
Eclipse JKube version
SNAPSHOT
Component
Kubernetes Maven Plugin
Apache Maven version
other (please specify in additional context)
Gradle version
None
Steps to reproduce
mvn -fmaven-it k8s:build
Expected behavior
Buildpacks build should detect the configured directory via the build tool. It shouldn't assume project directory as the one from which build process is initiated.
JKube should pass the project using
--path
flag inpack
CLI argumentsRuntime
Kubernetes (vanilla)
Kubernetes API Server version
1.25.3
Environment
Linux
Eclipse JKube Logs
Sample Reproducer Project
https://github.com/rohankanojia-forks/jkube-buildpacks-poc-testing
Additional context
No response
The text was updated successfully, but these errors were encountered: