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
{{ message }}
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.
Currently, Jib builder always use the latest version of the released plugin. For consistency/reproducibility, user may want to specify a specific version of Jib.
Add JIB_VERSION argument and default to RELEASE.
In the Jib step, use plugin coordinate com.google.cloud.tools:jib-maven-plugin:${JIB_VERSON}:build
The text was updated successfully, but these errors were encountered:
hmm, i wonder if the version here will override the actual plugin version specified by the pom?
another way of doing this to specify the plugin version in the build file. that's actually really good too.
Yea, the user can definitely specify the plugin version in the build file, but the JIB_VERSION build template argument can be made to override that (so a default empty JIB_VERSION would call com.google.cloud.tools:jib-maven-plugin::build, which would use the project-specified version).
Currently, Jib builder always use the latest version of the released plugin. For consistency/reproducibility, user may want to specify a specific version of Jib.
Add
JIB_VERSION
argument and default toRELEASE
.In the Jib step, use plugin coordinate
com.google.cloud.tools:jib-maven-plugin:${JIB_VERSON}:build
The text was updated successfully, but these errors were encountered: