takari / maven-wrapper

The easiest way to integrate Maven into your project!

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Exception: System.IO.DirectoryNotFoundException: Could not find a part of the path '...\vsts-agent-win-x64-2.131.0\_work\r7\a\Content\settings.xml'

opened this issue · comments

I am using the below release configuration and by using it i am executing the .exe file from cmd. In the release configration, for cmd i set 'Tool' to "$(System.DefaultWorkingDirectory)\_23 April Config-clone\drop-2\P.B.Dep\bin\Sumit\P.B.D.exe"

But I'm getting the error:
Exception: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\droVM123\Downloads\vsts-agent-win-x64-2.131.0\_work\r7\a\Content\settings.xml'on deployment.

Here is the error log for the cmd run:

2018-04-26T08:23:05.2636416Z ##[section]Starting: Run
2018-04-26T08:23:05.2639275Z ==============================================================================
2018-04-26T08:23:05.2639500Z Task         : Command Line
2018-04-26T08:23:05.2639586Z Description  : Run a command line with arguments
2018-04-26T08:23:05.2639698Z Version      : 1.1.3
2018-04-26T08:23:05.2639778Z Author       : Microsoft Corporation
2018-04-26T08:23:05.2639870Z Help         : [More Information](https://go.microsoft.com/fwlink/?LinkID=613735)
2018-04-26T08:23:05.2639991Z ==============================================================================
2018-04-26T08:23:05.2725561Z ##[command]"C:\Users\droVM123\Downloads\vsts-agent-win-x64-2.131.0\_work\r7\a\_23 April Config-clone\drop-2\P.B.Dep\bin\Sumit\P.B.D.exe" 
2018-04-26T08:23:05.6906148Z Exception: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\droVM123\Downloads\vsts-agent-win-x64-2.131.0\_work\r7\a\Content\settings.xml'.
2018-04-26T08:23:05.7260207Z ##[error]Process completed with exit code 1.
2018-04-26T08:23:05.7282176Z ##[section]Finishing: Run

Other info:
The issue is only for the release. I'm using VSTS and have configured a server(Windows Server 2012 R2) for the build + release & uses MSBuid 14 for the build.

I cant tell how this bug is related