JibServiceUtil pushes separate images for additional tags specified in build configuration

[rohanKanojia]

Discussed in #2283

^{Originally posted by maodia July 17, 2023}
Hi，i have a question about the pushed image and tags when i use the jib build strategy ， so i need a answer or advice.
We use the Harbor for docker image registry, and when we use the default build strategy and the jib build strategy, the image and tags display in the Harbor web view is very different.

Here is the image define fragment in my pom file:

 <image>
      <name>registry.cmread.com/mgsc/demo4k8s-service-consumer</name>
       <build>
           <from>registry.cmread.com/library/openjdk:11-jdk</from>
           <tags>
               <tag>develop</tag>
               <tag>1.0.0</tag>
           </tags>
           <ports>
                 <port>8080</port>
            </ports>
            <assembly>
                 <name>app</name>
            </assembly>
       </build>
 </image>

this is a image of one pushed docker image with three tags display in the harber when we use the default build strategy, and it is what we expect:

this is a image of three pushed docker image with three tags display in the harber when we use the jib build strategy, and it is not what we expect:

[rohanKanojia]

We need to make changes in JibServiceUtil as discussed in #2283 (reply in thread)