Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-59500

Downstream pipelines are not triggered when the artifact has type docker-info

    Details

    • Similar Issues:

      Description

      Our standard is to build a SpringBoot fatjar containing one micro service, and then a docker image of it.

      We use the [dockerfile-maven-plugin|https://github.com/spotify/dockerfile-maven] for the last part, and in particular its docker-info jars to record maven dependencies between images.

      But these dependencies are not seen by the plugin, and thus dependent builds are not triggered.

      The bad thing is :

      • the docker-info jar, when produced, is recorded with type=docker-info and classifier=docker-info
      • when consumed as a dependency, it is with type=jar and classifier=docker-info (even if forcing the type in the POM)

        Attachments

          Issue Links

            Activity

            falcon benoit guerin created issue -
            falcon benoit guerin made changes -
            Field Original Value New Value
            Link This issue relates to JENKINS-50475 [ JENKINS-50475 ]
            falcon benoit guerin made changes -
            Link This issue relates to JENKINS-50205 [ JENKINS-50205 ]
            falcon benoit guerin made changes -
            Link This issue relates to JENKINS-50099 [ JENKINS-50099 ]
            falcon benoit guerin made changes -
            Attachment downstream-spy.log [ 48846 ]
            Attachment upstream-spy.log [ 48847 ]
            Hide
            falcon benoit guerin added a comment -

            Attached are extracts of spy logs from upstream project (producing the docker-info jar) and downstream project (consuming it)

            Show
            falcon benoit guerin added a comment - Attached are extracts of spy logs from upstream project (producing the docker-info jar) and downstream project (consuming it)
            Hide
            falcon benoit guerin added a comment -

            I think we should consider that two Maven artefacts having same groupId, artifactId, version and same type or null classifier or same classifier, are the sames

            Show
            falcon benoit guerin added a comment - I think we should consider that two Maven artefacts having same groupId, artifactId, version and same type or null classifier or same classifier, are the sames
            falcon benoit guerin made changes -
            Remote Link This issue links to "PR #226 (Web Link)" [ 23711 ]
            falcon benoit guerin made changes -
            Assignee Alvaro Lobato [ alobato ] benoit guerin [ falcon ]
            falcon benoit guerin made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            falcon benoit guerin made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            falcon benoit guerin made changes -
            Status In Review [ 10005 ] Fixed but Unreleased [ 10203 ]
            Resolution Fixed [ 1 ]
            falcon benoit guerin made changes -
            Resolution Fixed [ 1 ]
            Status Fixed but Unreleased [ 10203 ] Reopened [ 4 ]
            falcon benoit guerin made changes -
            Status Reopened [ 4 ] Fixed but Unreleased [ 10203 ]
            Resolution Fixed [ 1 ]
            falcon benoit guerin made changes -
            Status Fixed but Unreleased [ 10203 ] Resolved [ 5 ]

              People

              • Assignee:
                falcon benoit guerin
                Reporter:
                falcon benoit guerin
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: