[JIRA] (JENKINS-59147) VSTest fails differently after upgrading Jenikins to vr. 2.176.3

[ngre...@outlook.com (JIRA)]

Title: Message Title

Neftali Reyes created an issue   Jenkins / JENKINS-59147 VSTest fails differently after upgrading Jenikins to vr. 2.176.3 Issue Type: Bug Assignee: Joseph Petersen Components: vstestrunner-plugin Created: 2019-08-29 21:42 Environment: Jenkins for Windows running on Windows 10 Enterprise. Jenkins ver. 2.176.3, VSTest.Console plugin 1.0.8. Labels: jenkins Priority: Minor Reporter: Neftali Reyes I had Jenkins ver. 2.176.2 and vstest plugin 1.0.8 and there were problems with VSTest console.  Read that changes had been made in Jenkins to correct issue so I updated Jenkins to the latest rev. 2.276.3 and now VSTest.console seems to have other problems.  The relative path is not being used properly for the Test File. See the error below.  I have used the following three paths to the test file even including the physical path. bin\SeleniumProj.dll %WORKSPACE%\bin\SeleniumProj.dll "%WORKSPACE%\bin\SeleniumProj.dll" If this issue is already in the workings then disregard and close issue with a note indicating when would the issue be in. I understand the issue appears to be in the VSTest plugin. Perhaps I misunderstood the fix in Jenkins.  I have seen this same error before.   Error: no files matching the pattern %WORKSPACE%\bin\SeleniumProj.dll ERROR: no files matching the pattern %WORKSPACE%\bin\SeleniumProj.dll Finished: FAILURE Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.201582.1567114956000.2970.1567114980252%40Atlassian.JIRA.