-
New Feature
-
Resolution: Fixed
-
Major
-
None
I'd like to build a reporting system which would relate a released Maven artifact with the SCM changes which went into it. While I can get a list of build numbers and changesets from the REST API, one cannot currently fetch the Maven release numbers via the API, though they are displayed as tooltips and icons in the HTML view.
See the following service calls:
http://hudson-uri/job/<job name>/api/xml http://hudson-uri/job/<job name>/<build number>/api/xml
If either one or both of the calls below included an element with the Maven Release number then one could not only do:
http://hudson-uri/job/<job name>/<build number>/api/xml?xpath=//changeSet
but also:
http://hudson-uri/job/<job name>/<build number>/api/xml?xpath=//mavenReleaseVersion
and have all the major building blocks necessary to produce an automated reporting system. I would just need to create a post build action which would trigger some sort of indexer to come look at the URIs and grab the build, release numbers, and changeset data. Then I could ask my index to roll up changes between two arbitrary release versions.
A number of other requests are asking for variations on this theme of exposing Maven release number: see JENKINS-7487 and JENKINS-4126.
[JENKINS-8360] Expose Maven Release Version via REST API Call: i.e. link build no. and Maven version
You can get the last release version from
http://jenkinsserver/path/to/job/lastRelease/api/xml?xpath=/mavenModuleSetBuild/action/parameter[name=%22MVN_RELEASE_VERSION%22]/value/child::text()
Is this enough or is something more needed?
I could use this improvement too. Thanks!