With robocopy, exit codes 0 through 7 are considered successful codes so
your compare should be LEQ 7. http://ss64.com/nt/robocopy-exit.html
& https://support.microsoft.com/en-us/kb/954404
On Sunday, April 17, 2016 at 6:30:00 PM UTC-7, ok999 wrote:
>
> Thanks, yes the exit code is the cause for
Thanks, yes the exit code is the cause for this. Had to change my batch
lines like this
bat "robocopy %cd%${some_path1}${some_path2} ${path_to_node}\\a_folder1
file1 file2 ^& IF %ERRORLEVEL% LEQ 1 exit 0"
bat "robocopy %cd%${some_path1}${some_path3} ${path_to_node}\\a_folder2
file1 file2 ^& IF %ER
> On 17.04.2016, at 21:13, niristotle okram wrote:
>
> When the job comes to portion where the above code exist, it appears that the
> first line of robocopy is executed. And it exist.
Robocopy uses non-zero exit codes to indicate what it did rather than report a
problem/failure -- which is
Hi,
This is not directly a jenkins issue, but i am clueless on why this is
failing. All i trying to do is use robocopy (since we are using the damn-it
windows) to copy over 2 files from a jenkins dir to my nodes. The part of
the jenkins pipeline where its failing looks like this
bat "robocopy %cd%
