[HAP-503] Create a REST api in Jenkins plugin for Release Staging Created: 18/Jul/14  Updated: 14/Nov/17  Resolved: 21/Aug/14

Status: Resolved
Project: Jenkins Artifactory Plug-in
Component/s: Release Management
Affects Version/s: 2.2.3
Fix Version/s: 2.2.4

Type: New Feature Priority: Normal
Reporter: Michal Reuven (Inactive) Assignee: Eyal Ben Moshe (Inactive)
Resolution: Fixed Votes: 1
Labels: None

Issue Links:
is duplicated by HAP-613 Create a REST interface for Jenkins A... Will Not Implement


Many clients request Artifactory to have a Rest api to enable them perform the Jenkins release staging.
This ticket is somewhat related to ticket HAP-263

Comment by Kavin Kankeshwar [ 18/Jul/14 ]

This is a Critical feature for automating releases.

Comment by Eyal Ben Moshe (Inactive) [ 21/Aug/14 ]

The format of the API is as follows:
<Jenkins Server>/jenkins/job/<Project Name>/artifactory/staging?<Parameters List>

If you do not specify any of the below parameters, the Release Management API will use the values provided by the configured Artifactory Staging User Plugin.

Example (for a maven project):


A. Parameters list for Maven projects:

1. versioning

NONE: Use existing module versions
GLOBAL: One version for all modules
PER_MODULE : Version per module

2. releaseVersion
3. nextVersion
4. release.<Artifact GroupID>:<Artifact ID>
5. next.<Artifact GroupID>:<Artifact ID>
6. releaseBranch
7. createVcsTag
8. tagUrl
9. tagComment
10. nextDevelCommitComment
11. repositoryKey
12. stagingComment

B. Parameters list for Gradle projects:

1. versioning
2. releaseVersion
3. nextVersion
4. release.<Property version name in gradle.properties>
5. next.<Property version name in gradle.properties>

The full documentation will be soon available at:


Generated at Wed Jun 03 02:38:26 UTC 2020 using Jira 8.5.3#805003-sha1:b4933e02eaff29a49114274fe59e1f99d9d963d7.