[JIRA] (JENKINS-59500) Downstream pipelines are not triggered when the artifact has type docker-info

0 views
Skip to first unread message

benoit.guerin@gmail.com (JIRA)

unread,
Sep 24, 2019, 4:14:03 AM9/24/19
to jenkinsc...@googlegroups.com
benoit guerin created an issue
 
Jenkins / Improvement JENKINS-59500
Downstream pipelines are not triggered when the artifact has type docker-info
Issue Type: Improvement Improvement
Assignee: Alvaro Lobato
Components: pipeline-maven-plugin
Created: 2019-09-24 08:13
Priority: Minor Minor
Reporter: benoit guerin

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)
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

benoit.guerin@gmail.com (JIRA)

unread,
Sep 24, 2019, 4:24:02 AM9/24/19
to jenkinsc...@googlegroups.com
benoit guerin updated an issue
Change By: benoit guerin
Attachment: downstream-spy.log
Attachment: upstream-spy.log

benoit.guerin@gmail.com (JIRA)

unread,
Sep 24, 2019, 4:25:02 AM9/24/19
to jenkinsc...@googlegroups.com
benoit guerin commented on Improvement JENKINS-59500
 
Re: Downstream pipelines are not triggered when the artifact has type docker-info

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

benoit.guerin@gmail.com (JIRA)

unread,
Sep 24, 2019, 4:29:05 AM9/24/19
to jenkinsc...@googlegroups.com

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

benoit.guerin@gmail.com (JIRA)

unread,
Sep 24, 2019, 4:31:01 AM9/24/19
to jenkinsc...@googlegroups.com
Change By: benoit guerin
Status: In Progress Review

benoit.guerin@gmail.com (JIRA)

unread,
Sep 24, 2019, 4:31:02 AM9/24/19
to jenkinsc...@googlegroups.com
benoit guerin started work on Improvement JENKINS-59500
 
Change By: benoit guerin
Status: Open In Progress

benoit.guerin@gmail.com (JIRA)

unread,
Sep 24, 2019, 4:31:02 AM9/24/19
to jenkinsc...@googlegroups.com
benoit guerin assigned an issue to benoit guerin
Change By: benoit guerin
Assignee: Alvaro Lobato benoit guerin

benoit.guerin@gmail.com (JIRA)

unread,
Feb 14, 2020, 3:33:05 AM2/14/20
to jenkinsc...@googlegroups.com
Change By: benoit guerin
Status: In Review Fixed but Unreleased
Resolution: Fixed

benoit.guerin@gmail.com (JIRA)

unread,
Feb 14, 2020, 3:34:03 AM2/14/20
to jenkinsc...@googlegroups.com
Change By: benoit guerin
Resolution: Fixed
Status: Fixed but Unreleased Reopened

benoit.guerin@gmail.com (JIRA)

unread,
Feb 14, 2020, 3:36:02 AM2/14/20
to jenkinsc...@googlegroups.com
Change By: benoit guerin
Status: Fixed but Unreleased Resolved

benoit.guerin@gmail.com (JIRA)

unread,
Feb 14, 2020, 3:36:03 AM2/14/20
to jenkinsc...@googlegroups.com
Change By: benoit guerin
Status: Reopened Fixed but Unreleased
Resolution: Fixed
Reply all
Reply to author
Forward
0 new messages