On Thu, Jul 3, 2014 at 9:31 AM, <[email protected]> wrote:
>
>
> We run our build.bat on a windows box. We are moving this into jenkins. One
> of the command line args is a UNC pathname. The batch script works fine on
> the windows machine in a cmd window. When I execute the same command in
> jenkins batch script, it cannot see the unc path somehow. The batch script
> has the following command which fails when it is run in jenkins:
>
> @rem Test if staging area exists. @set BuildResultsDir=%4 @if not exist
> "%BuildResultsDir%" (
> @echo.
> @echo. -ERROR- Arg4 StagingArea "%BuildResultsDir%" does not exist.
> @echo.
> @goto:eof )
>
> The error message in the log is: M:>setlocal enabledelayedexpansion
>
> -ERROR- Arg4 StagingArea "\wesrdbb5\Reef7.2Sust\Nightly_Build\CM03Build" does
> not exist.
>
> I tried changing %BuildResultsDir% to !BuildResultsDir! with no success.. any
> advice is welcome.
UNC paths work in general, but jenkins will be running as a different
user that probably doesn't have access. I've only used read-only
shares that permit guest access to avoid dealing with the quirks of
windows network authentication.
--
Les Mikesell
[email protected]
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
