-
Bug
-
Resolution: Not A Defect
-
Major
-
All latest versions
I have a local CVS repository, i.e. CVSROOT=/tmp/cvs_repo/cvs.
My job has a parameter of type "CVS Symbolic Name parameter" in order to allow the user to select a branch, a tag or the head. The parameter is called "tag_or_branch". See the first snapshot.
My job has a CVS repository defined, pointing to the folder specified above. I have set the location to "branch" and set the branch name to ${tag_or_branch}. See the second snapshot.
When triggering the build manually, I can choose the branch or head and it works fine.
My problem is that the polling always says that there are no changes even though I know there is a change. If I run the command (rlog...) manually it says that there is a change. Switching the location field to "head" instead of "branch" makes it work again. However it defeats the purpose of the parameter tag_or_branch.
Since polling can't take parametrized inputs (that would require asking the user where to poll each time a poll commenced), there is no way of it knowing what your parameter resolves to, so it doesn't try and resolve the parameter.
The only way to try and get round this would be get the user to provide a default value for polling with, use the last run's value, or to poll everything in the repository. None of these are really suitable since they're either not going to turn up changes on branches we may be interested in, or will trigger for changes that we don't care about.