Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

Missing ~\xxxx directory



  • If we set the working directory of a task to ~\bin the bni directory is not being automatically created hence we get the following exception when the task runs. The workaround is to create the bin directory manually.

    Should Buildmaster create the bin directory manually ?

    Temp Directory: C:\BuildMaster\_SVCTMP\_A23\_S0\TMP
    Source Directory: C:\BuildMaster\_SVCTMP\_A23\_S0\SRC
    Target Directory: C:\BuildMaster\_SVCTMP\_A23\_S0\WRK
    Server: WHOS888 (Id: 1)
    Initializing action...
    Initialization complete. Executing...
    Arguments: -m -e robots=off -nd -np -A*.sh http://artifactory:8081/artifactory/Cusmod/deployment-scripts/Client/
    Working Directory: C:\BuildMaster\_SVCTMP\_A23\bin
    Executing C:\Program Files (x86)\GnuWin32\bin\wget.exe
    An unhandled exception occurred while executing this action: System.ComponentModel.Win32Exception (0x80004005): The directory name is invalid at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo) at Inedo.BuildMaster.Extensibility.Agents.LocalProcessBase`1.Start() at Inedo.BuildMaster.Extensibility.Actions.AgentBasedActionBase.ExecuteCommandLine(AgentProcessStartInfo startInfo) at NZCustomsServiceExtension.Actions.WGetFromArtifactoryAction.Execute() in c:\BuildMaster\_SVCTMP\_A7\_S0\SRC\NZCustomsServiceExtension\Actions\WGetFromArtifactoryAction.cs:line 95 at Inedo.BuildMaster.Extensibility.Actions.ActionBase.ExecuteInternal(IActionExecutionContext context, ExtensionConfigurerBase extensionConfigurer, Boolean resumeNextOnError, Boolean logErrorsAsWarnings)
    

    Product: BuildMaster
    Version: 4.2.6



  • We believe that it should not because it's most likely a mistake to specify a directory that doesn't exist as the working directory since presumably there could be files to work with, etc. in that directory.

    As you mentioned, the workaround is to create the directory before this step. I would just use mkdir in a PowerShell or Bash script.



Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation