|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I am not sure if this worked with previous versions. Used plugin versions are:
-Maven Project Plugin: 1.2
-Matrix Project Plugin: 1.2
-Parameterized Trigger plugin: 2.25
I suppose you could reproduce the problem by creating a parameterized Maven Project (_BUILD_ARTIFACT) that receives following string parameters: BASE_SCM_URL, ARTIFACT_NAME, ARTIFACT_BRANCH (default: "trunk"), PROJECT_GROUP, MAVEN_TARGETS (default: "clean install").
This job downloads sources from an SCM repository (we use Subversion) located at: ${BASE_SCM_URL}/${PROJECT_GROUP}/${ARTIFACT_NAME}/${ARTIFACT_BRANCH} and specifies as local module directory: ${ARTIFACT_NAME}
Build step consist of specifying pom.xml file with the ${MAVENN_TARGETS} in "Goals and options".
Then create a parameterized multi-configuration project for three different artifact names (you can define the AXIS as "ARTIFACT_NAME") with a build step that simply triggers the execution of _BUILD_ARTIFACT job passing the required paramters and checking "Block until the triggered projects finish their builds" option.