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
IntelliJ IDEA 2018.1 EAP (Ultimate Edition)
Build #IU-181.3494.3, built on February 6, 2018
IntelliJ IDEA EAP User
Expiration date: March 8, 2018
JRE: 1.8.0_152-release-1136-b5 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.13.3
...
[INFO] RUNNING Pushing new image
[INFO] Pushing new image : 0.172 ms
[INFO] Building and pushing image : 9203.004 ms
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 32.573 s
[INFO] Finished at: 2018-02-12T14:17:09-08:00
[INFO] Final Memory: 34M/786M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.google.cloud.tools:jib-maven-plugin:0.1.1-SNAPSHOT:build (default-cli) on project platform: Build image failed: file name 'app/classes/com/<really_long_path>/LocationIntegrationSettings$GenericDefaultEntryHolder.class' is too long ( > 100 bytes) -> [Help 1]
The text was updated successfully, but these errors were encountered:
Ah, thanks for the find! Looks like we just need to use a POSIX long file mode when we are building the layers. Will be adding a fix for this soon to be also released in v0.1.1.
Description of the issue:
When building with some long protobuf filenames, Jib breaks with an error that the filename is too long.
Expected behavior:
It should build anyways because we all know how long Java filenames can get, especially with paths included.
Steps to reproduce:
Environment:
Jib:
0.1.1-SNAPSHOT
Maven:
IntelliJ:
jib-maven-plugin
Configuration:Log output:
The text was updated successfully, but these errors were encountered: