:-)
>
> /James
>
>> -Original Message-
>> From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-
>> d...@googlegroups.com] On Behalf Of Ulli Hafner
>> Sent: 05 July 2013 10:29
>> To: jenkinsci-dev@googlegroups.com
>> Subject: Re: Buildhive is not sh
: jenkinsci-dev@googlegroups.com
> Subject: Re: Buildhive is not showing the latest artifact of a successful
> build
>
> 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
.m2release$m2release/
>
> /James
>
>> -Original Message-
>> From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-
>> d...@googlegroups.com] On Behalf Of Ulli Hafner
>> Sent: 03 July 2013 14:03
>> To: jenkinsci-dev@googlegroups.com
>> Subject: B
Behalf Of Ulli Hafner
> Sent: 03 July 2013 14:03
> To: jenkinsci-dev@googlegroups.com
> 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 c
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
