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
This commit is contained in:
parent
01469da7d3
commit
0369d8a958
@ -16,7 +16,6 @@ declare -a projectList=(
|
|||||||
"$path/Services/Location/Locations.API"
|
"$path/Services/Location/Locations.API"
|
||||||
"$path/Services/Marketing/Marketing.API"
|
"$path/Services/Marketing/Marketing.API"
|
||||||
"$path/Services/Payment/Payment.API"
|
"$path/Services/Payment/Payment.API"
|
||||||
"$path/Services/GracePeriod/GracePeriodManager"
|
|
||||||
"$path/Web/WebMVC"
|
"$path/Web/WebMVC"
|
||||||
"$path/Web/WebStatus"
|
"$path/Web/WebStatus"
|
||||||
)
|
)
|
||||||
@ -32,9 +31,9 @@ do
|
|||||||
pushd $path/$project
|
pushd $path/$project
|
||||||
rm -rf obj/Docker/publish
|
rm -rf obj/Docker/publish
|
||||||
echo -e "\e[33m\tRestoring project $project"
|
echo -e "\e[33m\tRestoring project $project"
|
||||||
dotnet restore
|
dotnet restore --verbosity minimal
|
||||||
echo -e "\e[33m\tBuilding and publishing $project"
|
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
|
popd
|
||||||
done
|
done
|
||||||
|
|
||||||
|
@ -11,7 +11,7 @@ services:
|
|||||||
# Next line is using the .sln file to compile all the projects.
|
# 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)
|
# 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.
|
# 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.
|
# 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"
|
command: /bin/bash -c "pushd ./src/Web/WebSPA && npm rebuild node-sass && popd && pushd /cli-linux && ./build-bits-linux.sh /src"
|
||||||
|
Loading…
x
Reference in New Issue
Block a user