Hello all, I'm using the Subversion plugin to allow triggering jobs via the subversion post-commit hook (here: https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin) and it works perfectly. Recently, we added some build jobs that now require an additional parameter to be passed in (they are configured to use the List Subversion Tags parameter plugin) so a branch or tag can be specified as a parameter to the build job.
Normally, I'd use the URL to the specific job and pass the branch/tag as a URL parameter, but, its not conducive to do that in this scenario because there could be up to 200-300 different builds; and explicitly defining 200-300 URLs in the post-commit hook is just, well.. I just don't want to have to do that. So, on to my question... is there a way to pass an additional parameter to the wget call that tells the Jenkins job to poll (i.e.: wget ... http://myjenkinsserver/subversion/{UUID}/notifyCommit?rev=$REV&myparam=$BRANCH)? Or, is there a more standardized way of accomplishing what I need? Oh, I've toyed with creating a new plugin that leverages the work done on the Subversion plugin, and I have added the needed parameter, but, I may simply not be triggering the build properly with parameters, because any down-stream builds that result from the triggered build seem to ignore the parameters; but the job actually triggered does build successfully. Or, am I just nuts for even attempting to do this insane generic approach? Oh! My Jenkins version is: 1.529 with all installed plugins at the latest versions (as of 1.529). Thanks in advance for your suggestions/comments! Randy -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
