Actually wait, you need to use ${ProjectBranchName} in the view field, not
the client name field, just as Mark suggested.
On Monday, 12 November 2012 20:05:13 UTC-7, Rob Petti wrote:
>
> This should already be working. What version of the plugin are you
> running? You may need to update to the latest.
>
> On Monday, 12 November 2012 07:43:10 UTC-7, RolfB wrote:
>>
>> I wish to have a parameterized Jenkins build which builds projects from a
>> Perforce database based on a parameterized location within the Perforce
>> database. Can anyone advise how to achieve this with the Jenkins Perforce
>> plug-in?
>>
>> To this end I attempted setting up a Matrix build with the "Workspace"
>> field in "Project Details" of the "Perforce" "Source Code Management" to
>> either "jenkins_branch_${ProjectBranchName}" or
>> "jenkins_branch_$ProjectBranchName". This is not expended in this field,
>> as the console output includes:
>> /usr/local/bin/p4 -s changes -s submitted
>> //jenkins_branch_${ProjectBranchName}/...@62994,@63043
>> Sync'ing workspace to changelist 63043.
>> [MonitorP4ProjectlBranch] $ /usr/local/bin/p4 -s sync
>> //jenkins_branch_${ProjectBranchName}/...@63043
>> Caught exception communicating with perforce. Errors encountered while
>> syncing: error: //jenkins_branch_${ProjectBranchName}/...@63043 - no such
>> file(s).
>>
>> thus I suspect I am using the wrong approaching.
>>
>> Thanks,
>> Rolf
>>
>
