Hi,
you are using a quite outdated and unsupported plugin (see its wiki page).
And additionally it unsecessarily uses a patched SVN plugin.
A much easier way is to just add "@<revision_no>" to your SVN URL.
You can even use build parameters for this, like
"<svn_url>@${parameter_name}"
Hope this helps!
Harald
(btw.: this is a OSS mailing list, not "Support" :-)
On Tuesday, 30 August 2016 08:04:02 UTC+2, [email protected] wrote:
>
> Hello Support,
>
> Recently we have got an issue with Subversion Release Manager plugin where
> we cannot take build using specific revision number. We have noticed the
> issue after upgrading Jenkins to version Jenkins ver. 2.7.1
> <http://jenkins-ci.org/> from Jenkins 1.6. Earlier we were able to take
> builds using specific revision number using Subversion Release Manager
> plugin. But after upgrade, it always take build using HEAD revision number
> only even though we choose specific revision number while taking the build.
> Is this reported issue and do we have any fix for this ?
>
> In order to resolve this issue for the time being, we had to downgrade the
> Jenkins version back to ver. 1.639
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/aa1799a9-4eb0-4254-ad1b-bbd030185957%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
