Julia: add windows-cpu build

[iblislin]

• Julia v0.7
• Julia v1.0

[iblislin]

well, why errors in powershell script are not considered as build failure?
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Fwindows-cpu/detail/PR-13937/2/pipeline/82#step-151-log-22

[marcoabreu]

Yeah Powershell is not very smart unfortunately :( Have a look at how we do it here: https://github.com/apache/incubator-mxnet/blob/e8a2b8b9fdafaccbf65397cec142fffcae2289b7/ci/windows/test_py3_cpu.ps1#L27

What this basically does is evaluating the previous return code and then manually throwing an exception. I think there's no way to have a set -e like we have in bash...

[marcoabreu]

Btw here's the RFC to add native error handling to Powershell. Feel free to give it a +1 PowerShell/PowerShell-RFC#88

[iblislin]

This PR is ready for review.

[marcoabreu]

Could you elaborate that's the deal with

powershell.exe : [ Info: Path `C:\jenkins_slave\workspace\ut-julia07-cpu\julia-depot\dev\MXNet` exists and looks like the correct package, using existing path instead of cloning

At C:\jenkins_slave\workspace\ut-julia07-cpu@tmp\durable-9d0a0ccf\powershellWrapper.ps1:3 char:1

+ & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Comm ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: ([ Info: Path `C...tead of cloning    :String) [], RemoteException

    + FullyQualifiedErrorId : NativeCommandError

It's flagged as an error, doesn't seem like one and isn't handled like one.

[iblislin]

Still not sure which line causes that message.
Will get a windows machine to figure out it later.

[marcoabreu]

LGTM, thanks for iterating on this!

Besides the nit about the comment, good to ship from my side.

[lebeg]

Looks good, only 4 and 5 minutes for the testing parts