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

Reply via email to