![]() |
|
|
|
|
Change By:
|
Christian Galsterer
(11/Jan/14 1:09 PM)
|
|
Description:
|
Currently the upstream candidate resolution mechanism for "Build whenever a SNAPSHOT dependency is built" only considers Maven install and deploy lifecycle when there is more than one possible upstream build
for the *same* artifact
. In this case the
name
tiebreaker kicks in, which then determines the upstream build comparing by the job name. This is a reproducible behaviour but doesn't cater for the following situation as then the "wrong" build is selected depending on your naming strategy.
If you want to split your job into two steps where the first step verifies that your maven project compiles and all test are successful and in the second step one then upload the new artefacts to your remote repository (if the first step works fine) this works fine if you run the first step with "mvn clean verify" and the second step with "deploy" and there is no other upstream candidate. It doesn't work when there are other possible candidates (e.g. a static code analysis build of the
*
same
*
artefact) as then the tiebreaker kicks in and the the "wrong" build is selected (see above).
Example
Artifact A has the following two builds
- A_1 (CI, verify->deploy)
- A_2 (Static code analysis, which only compiles)
Artifact B depends on artifact
There should be an automatic upstream build from B to A_1 and not A_2.
In order to make the "Build whenever a SNAPSHOT dependency is built" feature working for the above sitatuation the algorithm to determine the upstream build should not only consider the install and deploy lifecycle phase, but also the verify phase.
|
|
|
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
