[JIRA] [tfs-plugin] (JENKINS-33117) Workspace name not parsed properly if a variable
Title: Message Title Olivier Dagenais assigned an issue to Olivier Dagenais Jenkins / JENKINS-33117 Workspace name not parsed properly if a variable Change By: Olivier Dagenais Assignee: redsolo Olivier Dagenais Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [tfs-plugin] (JENKINS-33117) Workspace name not parsed properly if a variable
Title: Message Title
Ian Williams created an issue
Jenkins / JENKINS-33117
Workspace name not parsed properly if a variable
Issue Type:
Bug
Assignee:
redsolo
Components:
tfs-plugin
Created:
24/Feb/16 2:59 AM
Environment:
Jenkins 1.609.1, tfs-plugin-4.0.0, Linux
Priority:
Minor
Reporter:
Ian Williams
Create Jenkins job with Advanced Project Options Use custom workspace = {{./$ {JOB_NAME##*/}}} Note that this is described to drop the folder from job name in http://jenkins:8080/env-vars.html/ Output Logs: {{Created workspace 'My-Build-Job-Slave'. Mapping '$/path/to/tfs/code' to local folder '/path/to/user/workspace/${JOB_NAME##*/}
' in workspace 'My-Build-Job-Slave'... FATAL: hudson.remoting.ProxyException: com.microsoft.tfs.core.exceptions.TECoreException: TF203003: You cannot specify a wildcard character for this working folder. The only wildcard character allowed is an '*' to map a Team Foundation Server folder and its immediate child items to your workspace. java.lang.RuntimeException: hudson.remoting.ProxyException: com.microsoft.tfs.core.exceptions.TECoreException: TF203003: You cannot specify a wildcard character for this working folder. The only wildcard character allowed is an '*' to map a Team Foundation Server folder and its immediate child items to your workspace. }}
Also, seems
[JIRA] [tfs-plugin] (JENKINS-33117) Workspace name not parsed properly if a variable
Title: Message Title
Ian Williams updated an issue
Jenkins / JENKINS-33117
Workspace name not parsed properly if a variable
Change By:
Ian Williams
Create Jenkins job with Advanced Project OptionsUse custom workspace = {{ ./${JOB_NAME##*/} }} Note that this is described to drop the folder from job name in http://jenkins:8080/env-vars.html/Output Logs: {{ Created workspace 'My-Build-Job-Slave'.Mapping '$/path/to/tfs/code' to local folder '/path/to/user/workspace/${JOB_NAME##*/}' in workspace 'My-Build-Job-Slave'...FATAL: hudson.remoting.ProxyException: com.microsoft.tfs.core.exceptions.TECoreException: TF203003: You cannot specify a wildcard character for this working folder. The only wildcard character allowed is an '*' to map a Team Foundation Server folder and its immediate child items to your workspace.java.lang.RuntimeException: hudson.remoting.ProxyException: com.microsoft.tfs.core.exceptions.TECoreException: TF203003: You cannot specify a wildcard character for this working folder. The only wildcard character allowed is an '*' to map a Team Foundation Server folder and its immediate child items to your workspace. }} Also, seems related to similar parsing problem in [https://issues.jenkins-ci.org/browse/JENKINS-29006] and [https://issues.jenkins-ci.org/browse/JENKINS-30442]
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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
