Ah, I see. Seems that we should improve the usability of the maven project type;-) At least for single module builds it is quite cumbersome to have some information shown only on submodule level and not on the top level. Shouldn't every UI part on the submodule level show the aggregation on the top-level? (As this is done for test or code analysis results?)
Ulli Am 04.07.2013 um 16:37 schrieb James Nord (jnord) <[email protected]>: > Hi Ulli, > > It already does - e.g. > > https://jenkins.ci.cloudbees.com/job/plugins/job/m2release-plugin/lastStableBuild/org.jvnet.hudson.plugins.m2release$m2release/ > > /James > >> -----Original Message----- >> From: [email protected] [mailto:jenkinsci- >> [email protected]] On Behalf Of Ulli Hafner >> Sent: 03 July 2013 14:03 >> To: [email protected] >> Subject: Buildhive is not showing the latest artifact of a successful build >> >> Would it be possible to archive the latest artifact (*.hpi file) in our >> plug-in jobs >> in Buildhive? Then I can point reporters of a bug to the latest snapshot >> release >> for a test... >> >> Ulli >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" 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/groups/opt_out. >> > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" 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/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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/groups/opt_out.
