-
New Feature
-
Resolution: Unresolved
-
Major
-
None
The reason why we require this information is to be able to for example
determine the maven coordinates of the parent pom to for example be able
to track individual builds across multiple different applications and
servers.
The information from the parent pom, if available, would then be exported
via JSON/XML/... as part of the mavenModuleSetBuild/mavenArtifacts/
moduleRecord/pomArtifact subtree made accessible via the parent property,
e.g.
<mavenModuleSetBuild> <mavenArtifacts> <moduleRecord> <pomArtifact> <artifactId>module1</artifactId> <groupId>org.example.sample</groupId> <type>jar</type> <version>0.0.1-SNAPSHOT</version> <parent> <artifactId>parent</artifactId> <groupId>org.example.sample</groupId> <type>pom</type> <version>0.0.1-SNAPSHOT</version> </parent> </pomArtifact> </moduleRecord> <moduleRecord> <pomArtifact> <artifactId>parent</artifactId> <groupId>org.example.sample</groupId> <type>pom</type> <version>0.0.1-SNAPSHOT</version> </pomArtifact> </moduleRecord> </mavenArtifacts> </mavenModuleSetBuild>
See the pull request for a working patch here
https://github.com/jenkinsci/jenkins/pull/361