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

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

    XMLWordPrintable

Details

    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 added a comment -

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

            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)
            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 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

            People

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

              Dates

                Created:
                Updated:
                Resolved: