[JIRA] (JENKINS-60549) TFS plugin fails to detect history if multiple SCM steps are used in pipeline

[zi...@heavysoft.ru (JIRA)]

Title: Message Title

Anton Zimin created an issue   Jenkins / JENKINS-60549 TFS plugin fails to detect history if multiple SCM steps are used in pipeline Issue Type: Improvement Assignee: redsolo Components: tfs-plugin Created: 2019-12-19 22:28 Priority: Minor Reporter: Anton Zimin I have a pipeline with multiple SCM TFS checkouts: stage ('SCM') { steps { script { dir ('Dir1') { checkout([$class: 'TeamFoundationServerScm', credentialsConfigurer: [$class: 'AutomaticCredentialsConfigurer'], projectPath: '$/Repo1', serverUrl: 'http://example.com:8080/tfs', useOverwrite: true, useUpdate: false, workspaceName: 'Hudson-${JOB_NAME}-${NODE_NAME}-REPO1']) } dir ('Dir2') { checkout([$class: 'TeamFoundationServerScm', credentialsConfigurer: [$class: 'AutomaticCredentialsConfigurer'], projectPath: '$/Repo2', serverUrl: 'http://example.com:8080/tfs', useOverwrite: true, useUpdate: false, workspaceName: 'Hudson-${JOB_NAME}-${NODE_NAME}-REPO2']) } } } } AFAIU Jenkins can't detect changes since the last correctly because of the plugin limitations. recordWorkspaceChangesetVersion method adds TFSRevisionState action. Probably there will be 2 actions for every build. https://github.com/jenkinsci/tfs-plugin/blob/de8c46ab72f750019ffc14b5f3d43f12dc478093/tfs/src/main/java/hudson/plugins/tfs/TeamFoundationServerScm.java#L384 However, determineVersionSpecFromBuild gets the first action. https://github.com/jenkinsci/tfs-plugin/blob/de8c46ab72f750019ffc14b5f3d43f12dc478093/tfs/src/main/java/hudson/plugins/tfs/TeamFoundationServerScm.java#L367 Is there something I can do to fix the changelogs history? Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203653.1576794538000.13883.1576794540152%40Atlassian.JIRA.