Stage1 publishing copies binaries over to Stage2

[Sridhar-MS]

*** Building stage1 dotnet using downloaded stage0 ... ***
15:56:44 Publishing �[33mdotnet�[39m for �[33mDNXCore,Version=v5.0�[39m/�[33mubuntu.14.04-x64�[39m
15:56:46 Compiling �[33mMicrosoft.DotNet.ProjectModel�[39m for �[33mDNXCore,Version=v5.0�[39m
15:56:48 Copy From: /mnt/j/workspace/dotnet_cli/debug_ubuntu/artifacts/ubuntu.14.04-x64/stage1/bin/Microsoft.DotNet.ProjectModel.dll
15:56:48 To: /mnt/j/workspace/dotnet_cli/debug_ubuntu/artifacts/ubuntu.14.04-x64/stage2/bin/
15:56:48 Copy From: /mnt/j/workspace/dotnet_cli/debug_ubuntu/artifacts/ubuntu.14.04-x64/stage1/bin/Microsoft.DotNet.ProjectModel.pdb
15:56:48 To: /mnt/j/workspace/dotnet_cli/debug_ubuntu/artifacts/ubuntu.14.04-x64/stage2/bin/

Probably related to #4539.

[TheRealPiotrP]

@cdmihai is this something you want to pick up while you're thinking about eliminating post-compile scripts?

[cdmihai]

Yes, we were actually studying this exact behaviour yesterday when we were looking into taking them out.

We found out that the place-binary script always copies to stage2, indifferent of what you compile So compilation of stage 1 copies output to stage 2. Compilation of stage2 copies output over itself. This got us a bit puzzled about the meaning of the script so we removed it entirely and CLI still builds itself, with everything passing. :)

I'll put out a PR out next week (removing the scripts turns on incremental compilation and I still want to make sure that one works reasonably well ...)

[TheRealPiotrP]

Goal of the script is to enable dev cycle. I update dotnet-foo, I compile dotnet-foo [which replaces in stage2], I run dotnet-foo and my new bits are in place...

[cdmihai]

Solved by removing the place-binary script and enabling incremental build in the dev cycle. Developers should call build and set it to output in stage2.

Issue dotnet/cli#790 discusses more advanced mechanism to make the above easier.