[HAP-759] Support for Maven from within the pipeline plugin Created: 15/Jun/16  Updated: 14/Nov/17  Resolved: 25/Sep/16

Status: Resolved
Project: Jenkins Artifactory Plug-in
Component/s: None
Affects Version/s: None
Fix Version/s: 2.7.2

Type: Improvement Priority: High
Reporter: Alexei Vainshtein Assignee: Tamir Hadad
Resolution: Fixed Votes: 7
Labels: None

Issue Links:
depends on BI-369 Support maven/gradle within Artifacto... Resolved


Currently the support for pipeline plugin is for uploading and downloading artifacts and build info. We should support Maven as well

Comment by Giovanni Toraldo [ 11/Aug/16 ]

Is there any way to publish a maven artifact using DSL in a pipeline job without explicit support?

This thing is really blocking my workflow.

Comment by Eyal Ben Moshe (Inactive) [ 11/Aug/16 ]

Hi Giovanni,
Yes, you can have your maven artifacts published to Artifactory even before the maven DSL for Artifactory is released. When the DSL is released, using it should be the most convenient and therefore highly recommended for all maven builds from a Pipeline script.
Till this is released, you can use one of the following options:
1. User the Maven Artifactory Plugin (a maven plugin that you can install inside your pom file). The plugin provides: checksum deployment, atomic deployment at the end of the build and build-info publication:
2. User maven's default deploy goal, Less recommended than option #1 above, because it does not provide any of the Artifactory Plugin advantages, but it will get your artifacts deployed in Artifactory.

Comment by Giovanni Toraldo [ 12/Aug/16 ]

3. Create a maven-style Jenkins job configured with Jenkins Artifactory Plugin for only deploying artifacts, called from the pipeline job using job('project-deploy').

Thanks for your inputs.

Generated at Mon Jun 01 20:46:45 UTC 2020 using Jira 8.5.3#805003-sha1:b4933e02eaff29a49114274fe59e1f99d9d963d7.