Jenkins: How do I use the Parameterized Trigger Plugin and pass a subversion revision?

Question

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 d

Answer 1

Turns out, like the test case says, this was all I had to do. I tested this by committing to U, then committed again while it was building. Once D started building, it grabbed the first commit, not the latest. That's how I tested it was working.

Better feedback would be appreciated, but at least I know it's working.