question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

If no version is specified, the tag should default to "latest" instead of "unspecified"

See original GitHub issue

Description of the issue:

When running ./gradlew jibDockerBuild the Docke rimage is always also tagged with “unspecified” even if a tag is specified via jib.to.tags.

Expected behavior:

Only the tags specified via jib.to.tags are used to tag the Docker image.

Steps to reproduce:

Run ./gradlew jibDockerBuild with the configuration as mentioned below. See https://github.com/heremaps/oss-review-toolkit/blob/jib/cli/build.gradle to reproduce.

Environment:

Ubuntu 18.04

jib-gradle-plugin Configuration:

plugins {
    id 'com.google.cloud.tools.jib' version '0.9.11'
}

jib.to.tags = ['latest']

Log output:

Parallel execution with configuration on demand is an incubating feature.
Tagging image with generated image reference cli:unspecified. If you'd like to specify a different tag, you can set the jib.to.image parameter in your build.gradle, or use the --image=<MY IMAGE> commandline flag.
warning: Base image 'gcr.io/distroless/java' does not use a specific image digest - build may not be reproducible

Containerizing application to Docker daemon as cli:unspecified, cli...

Getting base image gcr.io/distroless/java...
Building dependencies layer...
Building classes layer...
Finalizing...
Loading to Docker daemon...

Container entrypoint set to [java, -cp, /app/resources:/app/classes:/app/libs/*, com.here.ort.Main]

Built image to Docker daemon as cli:unspecified, cli

BUILD SUCCESSFUL in 9s
68 actionable tasks: 1 executed, 67 up-to-date

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
chanseokohcommented, Oct 4, 2018

Makes sense, especially when considering that jib.to.image = 'cli' gives you cli:latest instead of cli:unspecified.

0reactions
coollogcommented, Oct 4, 2018

Yea, I think we can change the behavior to not include a default tag if the version is unspecified.

Read more comments on GitHub >

github_iconTop Results From Across the Web

maven dependency without version - Stack Overflow
It is impossible for maven to work without defining versions of the artifacts. They should be defined somewhere in dependencyManagement tag ...
Read more >
Explanation of the error messages for the W3C Markup Validator
This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use...
Read more >
Publish - electron-builder
Draft a new release. Set the “Tag version” to the value of version in your application package.json , and prefix it with v...
Read more >
git-tag Documentation - Git
When unspecified, defaults to %(refname:strip=2) . <tagname>. The name of the tag to create, delete, or describe. The new tag name must pass...
Read more >
azureml.pipeline.steps.python_script_step.PythonScriptStep ...
If unspecified, a default runconfig will be created. ... default value: None. An optional version tag to denote a change in functionality for...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found