Skip to content

outputPaths not used in jib and jibDockerBuild tasks #4371

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
realPyR3X opened this issue Mar 26, 2025 · 0 comments
Open

outputPaths not used in jib and jibDockerBuild tasks #4371

realPyR3X opened this issue Mar 26, 2025 · 0 comments

Comments

@realPyR3X
Copy link

Environment:

  • Jib version: latest
  • Build tool: gradle
  • OS: linux

Description of the issue:

Settings outputPaths as follows:

outputPaths {
def baseOutputPath = project.layout.buildDirectory.dir('jib').get().file("${appName}-${version}").toString()
tar = "${baseOutputPath}.tar"
digest = "${baseOutputPath}.digest"
imageId = "${baseOutputPath}.id"
imageJson = "${baseOutputPath}.json"
}

works as expected for jibBuildTar. However, they are not generated for the jib and jibDockerBuild tasks resulting in an error there is NoSuchFile

Expected behavior:

jib and jibDockerBuild produce the digest, imageId, and imageJson at the locations specified (they do generate the default names if outputPaths is empty).

Also the documentation does not document the imageJson (I discovered it from the code)

Steps to reproduce:

  1. set outputPaths with custom locations for digest, imageId, and imageJson
  2. run ./gradlew jibDockerBuild
  3. See it fail with NoSuchFile

Log output:

Execution failed for task ':jibDockerBuild'.

java.nio.file.NoSuchFileException: /path/to/my/digest

Additional Information:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants