Better handling of running script in subdirectory that does not exist

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Duplicate
    • None
    • Component/s: None
    • None

      When running a script on a Windows agent the following is what is written to the log when the subdirectory used is not present.

      command	20-Jan-2016 09:03:42	Beginning to execute external process for build 'RightNow Connector - PROJECT-PLAN - Default Job #751 (PROJECT-PLAN-JOB1-1)'\n ... running command line: \nC:\Users\bamboo\AppData\Local\Temp\PROJECT-PLAN-JOB1-1-ScriptBuildTask-752448684682570453.bat\n ... in: C:\build-dir\PROJECT-PLAN-JOB1-1\subdir\n ... using extra environment variables: ...

simple	20-Jan-2016 09:03:42	Failing task since return code of [C:\Users\bamboo\AppData\Local\Temp\PROJECT-PLAN-JOB1-1-ScriptBuildTask-752448684682570453.bat] was -1 while expected 0

      A quick check to ensure the subdirectory exists and appropriate logging would help the end user out a lot.

            Assignee:
            Unassigned
            Reporter:
            Warren
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: