IMO, this use case really needs to be specifically spelled out on the plugin's webpage/documentation.
Let's say I have a project named U for upstream and D for downstream. When U finishes building, I want D to checkout the same revision that U just built. U will always checkout HEAD.
Here's what I've done:
- In U, I added a "Post-build Actions" for "Trigger parameterized build on other projects".
- For "Projects to build" I typed in D and to only build when "Stable".
- I added a trigger for "Subversion revision".
- I saved this configuration
Now I don't know what I'm supposed to do next, but I get no feedback to indicate this is working. In fact, even this testcase that's committed to the plugin source suggests this is all I should have to do.
But, if I were to guess, I'd think I'm supposed to mark U as a parameterized build and add a parameter to it. This parameter should be named what U sends to D. But, if I've got the right idea, I don't know what I'm supposed to name this parameter. Neither the console log of D nor the console log of U mentions any new parameter.
I took a guess and created a String parameter in U named "SVN_REVISION" and defaulted it to -1, but that had no effect. Every time D triggers a build, SVN_REVISION is defaulted to -1.
This is the output of running export on the D project:
+ export
export BUILD_ID="2013-03-20_09-48-32"
export BUILD_NUMBER="4522"
export BUILD_TAG="jenkins-D-4522"
export BUILD_URL="http://my.jenkins.server.com:8081/job/D/4522/"
export EXECUTOR_NUMBER="2"
export HUDSON_COOKIE="8ec52f7a-d60d-4640-83a9-dbed7351b32a"
export HUDSON_HOME="/opt/hudson"
export HUDSON_SERVER_COOKIE="633967fcd1d6f7b38a85