Monish Ratanji added a comment - 2020-09-29 21:19 Hello! Would it be possible to switch to using a scripted or declarative pipeline? You should be able to invoke the Groovy string interpolation that way. Here's an example of what my company is doing: script { def tfsCheckout = [$class: 'TeamFoundationServerScm', credentialsConfigurer: [$class: 'AutomaticCredentialsConfigurer'], projectPath: '$/some/path', serverUrl: "${env.TFS_SERVER_URL}, workspaceName: "${env.JOB_NAME}-${env.BUILD_NUMBER}"] def tf_data = checkout tfsCheckout env.TFS_CHANGESET = tf_data.TFS_CHANGESET env.TFS_PROJECTPATH = tf_data.TFS_PROJECTPATH env.TFS_SERVERURL = tf_data.TFS_SERVERURL env.TFS_WORKFOLDER = tf_data.TFS_WORKFOLDER env.TFS_WORKSPACE = tf_data.TFS_WORKSPACE } By using the string interpolation we can leave the variable expansion to Jenkins itself rather than the TFS plugin. If you want to continue using Freestyle jobs, I'm afraid I don't have much of a solution. The TFS plugin only expands a few specific variables for the Workspace name (JOB_NAME, USER_NAME, NODE_NAME). You can find the source code here: https://github.com/jenkinsci/tfs-plugin/blob/aea4ce0f1fd82668b1ead7e2aade2ffe36a32a10/tfs/src/main/java/hudson/plugins/tfs/util/BuildVariableResolver.java#L32 I could be completely wrong here though, so someone please correct me if I am wrong

Ian Williams added a comment - 2021-09-12 09:00 redsolo is no longer maintaining plugin; unassigned issues