[FIXED JENKINS-22568] Subversion polling does not work with parameters.

[christ66]

Currently subversion polling does not work with parameters. This code changes polls using the DEFAULT option. If there is a choice parameter, it will choose the FIRST option. This will also expand anything that is $VAL or ${VAL}.

[cloudbees-pull-request-builder]

plugins » subversion-plugin #384 SUCCESS
This pull request looks good

[jenkinsadmin]

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

[oleg-nenashev]

It could be useful to have an API plugin for variables resolution.
For example, MacroStringHelper from /jenkinsci/perforce-plugin#54 , provides the extensive variables substitution.

I can split the resolver into a separate API plugin if somebody wants to use it

[christ66]

That doesn't sound like a bad idea. I bet a lot of SCM builders or others would like to use an API like this.

[cloudbees-pull-request-builder]

plugins » subversion-plugin #386 SUCCESS
This pull request looks good

[jglick]

I am sure there is a utility in Jenkins core to do macro expansion which you should be using.

[stephenc]

@christ66 could probably do that... but IIRC the correct utility is actually in a plugin because there are multiple ways to expand tokens or something... anywho I'll leave it up to @christ66 how he wants to respond

[smruti-sahoo]

Hi - I'm facing the same issue with git poll SCM
Global environment variable are not being picked up during poll SCM

Could someone please help me to solve this issue ?

I tested it on
Jenkins 1.6 and 2.1(Recent version)
git 2.4.2 and 2.4.4 (Recent version)

[recena]

@smruti-sahoo Please, fill a Jira issue with a step by step to reproduce the bug.

[smruti-sahoo]

@recena Thanks - I've raised JENKINS-34603
I found a similar issue raised around a year before JENKINS-26315 but no update there, hence raised a new one