[JIRA] (JENKINS-3207) Allow check out of specific revision from Subversion via REVISION parameter
Title: Message Title
Helene W commented on JENKINS-3207
Re: Allow check out of specific revision from Subversion via REVISION parameter
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")
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-3207) Allow check out of specific revision from Subversion via REVISION parameter
Title: Message Title
Sven Keller commented on JENKINS-3207
Re: Allow check out of specific revision from Subversion via REVISION parameter
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
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
