dotnet-installer/scripts
Eric Erhardt a3ab4d16d1 Fix the package cache on CI on Unix.
On the CI machines, the $HOME variable is redirected to the artifacts folder, which is under the repo root. The package cache is using $HOME. Thus between runs, the cache is removed.

To fix this, change the package cache on CI runs to be outside of the repo.
2016-02-08 17:50:52 -06:00
..
build Cache NuGet packages on our CI server between builds. 2016-02-05 10:34:20 -06:00
common Fix the package cache on CI on Unix. 2016-02-08 17:50:52 -06:00
compile Upgrade stdlib and enable crossgen 2016-02-01 20:48:34 -08:00
configuration Add support for 'additionalArguments' in compilationOptions 2016-02-01 22:48:12 -08:00
crossgen Fix CentOS on the latest .Net Core. 2016-02-05 20:13:35 -06:00
docker update everything to DOTNET_CLI_VERSION 2016-01-13 02:22:53 -08:00
obtain sync install script params with PowerShell a bit 2016-02-04 09:58:26 -08:00
package Update package.sh 2016-02-04 15:46:58 -08:00
publish Responding to PR feedback, adding the OS names 2016-02-03 09:46:45 -08:00
test We still having issues when passing configuration to dotnet tests. This change makes dotnet build of tests and dotnet test commands always use debug build. We have issues #1267 and #1268 tracking fixes for this problem 2016-02-05 18:08:33 -08:00
ci_build.cmd Remove --no-cache from scripts 2016-01-23 09:53:51 -08:00
ci_build.sh Cache NuGet packages on our CI server between builds. 2016-02-05 10:34:20 -06:00
dev-dotnet.ps1 Clean up build scripts 2015-12-29 01:59:02 -08:00
dev-dotnet.sh Eliminate dead code and most relative paths 2015-12-29 02:34:10 -08:00
unuse-dev.ps1 Clean up build scripts 2015-12-29 01:59:02 -08:00
use-dev.ps1 Clean up build scripts 2015-12-29 01:59:02 -08:00