2012/7/30 Nord, James <
[hidden email]>:
> Hi Radim/Domi,
>
> It may also be because m2release plugin doesn't work well with Jenkins artifacts archival - see
https://issues.jenkins-ci.org/browse/JENKINS-7487?
>
Well, changing the behavior as suggested in this issue would make it
possible to workaround my problem and use copy artifact plugin.
Because copy artifact plugin gives me a choice to use build selected
by permalink 'last Release'. Surprisingly the code to look for
permalinks looks very similar in both plugins but Maven Deployment
Linker does not see permalinks that are not built in.
OK, I will file an issue.
Thanks,
Radim
> /James
>
>> -----Original Message-----
>> From:
[hidden email] [mailto:jenkinsci-
>>
[hidden email]] On Behalf Of domi
>> Sent: 30 July 2012 17:32
>> To:
[hidden email]
>> Subject: Re: Permalink to last Maven release builds usable in downstream
>> build?
>>
>> Hi Radim,
>> please fill an issue for this.
>> regards Domi
>>
>> On 30.07.2012, at 13:54, Radim Kubacki wrote:
>>
>> > Hi,
>> >
>> > I wanted to create a pipeline with a
>> > 1. Maven build that builds project including few of its subprojects
>> > and configured settings for Maven release build 2. manually executed
>> > downstream build to take deployed artifact(s) from latest Maven
>> > release build and push it to our testing enviroment (install RPM or
>> > deploy web application).
>> >
>> > I can do (2.) as a promotion but I do not like it. (I'd like to run
>> > some integration tests when the build is is deployed. Also there can
>> > be more staging levels so deployment pipeline looks like a better
>> > solution than a set of promotions.)
>> >
>> > I am almost there with the help of Maven Deployment Linker plugin
>> > (
http://wiki.hudson-ci.org/display/HUDSON/Maven+Deployment+Linker) but
>> > I can only choose to select last {|stable|successfull|failed} build as
>> > a source of my artifacts in this downstream build. Why isn't release
>> > build here when Maven plugin creates a permalink for lastRelease job?
>> > Configuring it to lastStable build is not an option: there can be some
>> > manual test between build and deployment build and even without the
>> > release build initiates new non-release build called from an SCM
>> > trigger when version update is pushed as a result of maven release.
>> >
>> > So is there a way how to access last release build data from some
>> > downstream build? If there is not how difficult it would be to add it?
>> >
>> > -Radim
>
>
> ________________________________
>
>
> **************************************************************************************
> This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the
[hidden email] and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
>
> NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
> **************************************************************************************
Locked
