Allow pushing multiple tags to registries

Description of the feature: Currently, in order to push multiple tags (of the same image) you must call jib multiple times. This is common with docker where you have the latest tag and version specific tags. I suggest there be a way to specify multiple tags within jib’s configuration.

Expected behavior:

jib {
    to {
        image = ["repo/name:tag", "repo/name:tag2", "repo2/name2:tag3"]
    }
}

Jib would handle this by building the container once and then (preferably in parallel) push the container with the given tags.

[coollog]

Hi everyone, we have released version 0.9.11 with the multi-tag configuration (<to><tags> for Maven, and to.tags for Gradle).

Example:

<configuration>
  ...
  <to>
    ...
    <tags>
      <tag>another</tag>
      <tag>and-yet-another</tag>
    </tags>
  </to>
</configuration>

@Techtony96 @Hronom @anuraaga @mjrsnyder @jeggy @sdavids @asaikali @itzg @davinkevin @nobecutan, @GuustavoPaiva, @sureshg

[coollog]

@Hronom Yes, that is possible, although that would require changing the schema of <image> to take a <reference> and <tags> field. I’d be hesitant to do that since it makes the usual case of having a single target image reference require <to><image><reference> rather than just <to><image>.

An alternative is to have <tags> be under the <to> tag:

<to>
  <image>registry.hub.docker.com/hronom/eureka-service</image>
  <tags>
    <tag>${git.commit.id}</tag>
    <tag>${project.version}</tag>
    <tag>latest</tag>
  </tags>
</to>

UPDATE: This is currently being implemented.

Tasks:

• Add additional tags to BuildConfiguration. #963
• Push to the additional tags. #968
• Build to Docker daemon with additional tags. #983
• Make build success message also display the additional tags. #982
• Add to.tags configuration for Gradle. #978
• Add the same for Maven. #1026
• Add additional tags for build to tarball?

Optimize:

• Parallelize pushing to multiple tags. #974 #1028