@msaxer:

look at dodok1's comment. Instead of your current URL (http://.../trunk) you just need to add the revision number to it. The URL will then look like http;//.../trunk@${MYREVISION} where MYREVISION is a parameter of your job. You can also replace ${MYREVISION} with a revision number, but I don't think that will have a useful purpose at all.

As mentioned on the thread on the wiki page, the Subversion plugin gets a RevisionParameterAction from the build which contains the Subversion revision of that build. No need to maintain a copy of the SubversionSCM code or modify CheckOutTask.

Hello,

I'm not sure if my proeblem is related to this topic but perhaps, somebody is still istening to this thread and can give some guidance.
I configured the job using SVNRM-plugin as described in the quick help and I can see my revision list in the "releases" menu.
However all the time I start a job from this list
(corresponding link looks like: http://myJenkins:8080/job/myJob/releases/build?revision=1934)
it always takes HEAD instead of the given revision number.

Where do I have to configure this in my job?
adding @1934 or @${REVISION} to the release SCM configuration does not help.

Sven

I have the same problem as Sven Keller.
When I add @${REVISION} at the end of the SVN url, than I don't see the revisions ("/trunk@$REVISION doesn't exist in the repository")

Hi,

Can you please provide me step by step solution for this issue even i am looking for "specific revision from Subversion via REVISION parameter" and the plugin "svn-release-mgr" which you have provided i am unable to find out.

Thanks,

Anup