Browse Source

Workaround (dotnet CLI set with verbosity minimal) so we don't get stdout errors when compiling from the Docker Linux "build containers" when doing the CLI build.

Related bug: https://github.com/Microsoft/msbuild/issues/2153#issuecomment-305375162
pull/297/head
Cesar De la Torre 7 years ago
parent
commit
8d42dfeb39
2 changed files with 3 additions and 3 deletions
  1. +2
    -2
      cli-linux/build-bits-linux.sh
  2. +1
    -1
      docker-compose.ci.build.yml

+ 2
- 2
cli-linux/build-bits-linux.sh View File

@ -32,9 +32,9 @@ do
pushd $path/$project
rm -rf obj/Docker/publish
echo -e "\e[33m\tRestoring project $project"
dotnet restore
dotnet restore --verbosity minimal
echo -e "\e[33m\tBuilding and publishing $project"
dotnet publish -o obj/Docker/publish
dotnet publish -c Release -o obj/Docker/publish --verbosity minimal
popd
done


+ 1
- 1
docker-compose.ci.build.yml View File

@ -11,7 +11,7 @@ services:
# Next line is using the .sln file to compile all the projects.
# Sometime there is an issue in msbuild exits the process before finishing building the bits: (https://github.com/Microsoft/msbuild/issues/2153)
# Random error: error MSB4017: The build stopped unexpectedly be cause of an unexpected logger failure.
#command: /bin/bash -c "pushd ./src/Web/WebSPA && npm rebuild node-sass && popd && dotnet restore ./eShopOnContainers-ServicesAndWebApps.sln && dotnet publish ./eShopOnContainers-ServicesAndWebApps.sln -c Release -o ./obj/Docker/publish"
#command: /bin/bash -c "pushd ./src/Web/WebSPA && npm rebuild node-sass && popd && dotnet restore ./eShopOnContainers-ServicesAndWebApps.sln --verbosity minimal && dotnet publish ./eShopOnContainers-ServicesAndWebApps.sln -c Release -o ./obj/Docker/publish --verbosity minimal"
# NOTE: Using build-bits-linux.sh from Linux build container exits before ending.
command: /bin/bash -c "pushd ./src/Web/WebSPA && npm rebuild node-sass && popd && pushd /cli-linux && ./build-bits-linux.sh /src"

Loading…
Cancel
Save