[JIRA] (JENKINS-47784) Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin

5 views
Skip to first unread message

Duc-Tai.Ly@inter.de (JIRA)

unread,
Nov 26, 2018, 8:01:02 AM11/26/18
to jenkinsc...@googlegroups.com
Tai Ly commented on New Feature JENKINS-47784
 
Re: Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin

Hi Cyrille Le Clerc,

I am also interested in this feature.

Sandra Parsick have you found an alternative solution to this feature?

 

Best regards,

Tai
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

mail@sandra-parsick.de (JIRA)

unread,
Nov 27, 2018, 4:37:02 AM11/27/18
to jenkinsc...@googlegroups.com

Hi Tai Ly

I use a Maven feature to simulate it. In Maven Deploy Plugin you can set the flag deployAtEnd.  This feature is experimental, but in my project it works as alternative solution.

 

Best regards,

Sandra

 

Duc-Tai.Ly@inter.de (JIRA)

unread,
Dec 3, 2018, 2:59:01 AM12/3/18
to jenkinsc...@googlegroups.com
Tai Ly commented on New Feature JENKINS-47784

Sandra Parsick thank you. I will check if this works for me.

 

Best regards,

Tai

cleclerc@cloudbees.com (JIRA)

unread,
Dec 29, 2018, 2:20:02 PM12/29/18
to jenkinsc...@googlegroups.com

Sandra Parsick , Tai Ly can you please explain me why you have to "re upload" the generated artifacts?
Do you have a problem of availability of your maven repository (Nexus, Artifactory...)?

mail@sandra-parsick.de (JIRA)

unread,
Jan 24, 2019, 6:52:02 AM1/24/19
to jenkinsc...@googlegroups.com

Cyrille Le Clerc I think, here is a misunderstanding. I don't want to do a "re upload". 

My use case can be described in following steps:

  1. As Maven goal, I run mvn clean install.
    #

cleclerc@cloudbees.com (JIRA)

unread,
Jan 29, 2019, 5:59:02 PM1/29/19
to jenkinsc...@googlegroups.com

Sandra Parsick your message seemed to have been truncated.

cleclerc@cloudbees.com (JIRA)

unread,
Jan 30, 2019, 4:15:02 AM1/30/19
to jenkinsc...@googlegroups.com
Cyrille Le Clerc edited a comment on New Feature JENKINS-47784
[~sparsick] your message seemed seems to have been truncated.

mail@sandra-parsick.de (JIRA)

unread,
Jan 30, 2019, 5:52:26 AM1/30/19
to jenkinsc...@googlegroups.com
Sandra Parsick edited a comment on New Feature JENKINS-47784
[~cleclerc] I think, here is a misunderstanding. I don't want to do a "re upload". 


My use case can be described in following steps:
# As Maven goal, I run {{mvn clean install.}}
# If this goal run successfully, I want to upload all artifact in bulk. In a classic Jenkins job, I used to use the Post Build Action "Deploy Maven Artifacts to repository" for this task.

In my comment to Tai, I only describe a workaround to simulate both step in a pipeline job. This feature of Maven deploy plugin is experimental, so that I would prefer a similar way in pipeline job as I used to have in a classic Jenkins job.

mail@sandra-parsick.de (JIRA)

unread,
Jan 30, 2019, 5:53:01 AM1/30/19
to jenkinsc...@googlegroups.com

mail@sandra-parsick.de (JIRA)

unread,
Jan 30, 2019, 5:54:02 AM1/30/19
to jenkinsc...@googlegroups.com

Cyrille Le Clerc Thank you for your hint. I edited it. No idea what went wrong on my first try.

tarunhasija3@gmail.com (JIRA)

unread,
Oct 23, 2019, 5:52:02 PM10/23/19
to jenkinsc...@googlegroups.com

Sandra Parsick we have a similar requirement of running the deploy is the post section on success of the build , can you please share the Workaround code you are using with the Maven Deploy Plugin 

 

This is what we have now , the below call triggers the maven stages again 

 post {
 post { 
 success {  
           sh 'mvn deploy'    
    }
 }
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

tarunhasija3@gmail.com (JIRA)

unread,
Oct 23, 2019, 5:53:03 PM10/23/19
to jenkinsc...@googlegroups.com

Cyrille Le Clerc will this feature be added to the plugin in near future ?

mail@sandra-parsick.de (JIRA)

unread,
Oct 25, 2019, 5:22:10 AM10/25/19
to jenkinsc...@googlegroups.com

Tarun Hasija you have two options:

 

First one is to configure the Maven Deploy Plugin in your  POM with the option

<deployAtEnd>true</deployAtEnd>

Because this feature of Maven Deploy Plugin is experimental you have to test whether it works in your project.

Second option is to add the Maven Extension "Deployer Extension" in your project. For more information, see https://github.com/khmarbaise/maven-deployer-extension
Reply all
Reply to author
Forward
0 new messages