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.
Currently on our CI builds, we point our NuGet cache under the repo. In between builds the repo gets deleted, thus the cache is lost.
This change moves the cache to %userprofile%\.nuget\packages on CI and dev boxes. On CI, we expire the cache after a day by default.
Add version badge generation using shields.io service. The badge
is uploaded to a fixed Azure BLOB location which can be referenced
from README.md. Since the badge creation is not crucial, do not fail the build
if it cannot be created.
Fix#1000
Rather than keep a map that will have to be constantly updated every time
a new argument gets added to a compiler, the 'additionalArguments' option
will allow users to directly add arguments to the underlying compiler.
add rid to all restores in test
Add Rid to appdep script, fix common
more script fixes!
fixes
script fix
script fix
Fix up the Runtests script
more fixes :)
remove publish todo
small fixes
small fixes
fix packaging test bug
Fix script bug
script changes
fix packaging test
NuGet task cancelled workaround
script fixes further
more script fixes, + workaround tweak
use build rather than compile in package command test
_nuget needs some RepoRoots
get the cats in line (d)
spaces
Fix Linux build breaks
add execution permissions
Pick up #999 Finish refactoring test scripts
remove auth
Reorder publishing to work!
fix rebase errors
fix more rebase errors
small fixes
- Project dependencies are always built into their specific folders and the main project is the only one that uses the output path and intermediate output path variable.
- Publish respects the output path for publish only, not compile as part of publish. This means that publishing multiple runtimes will stomp on each other. So don't do that. We can throw if you specify and output location and you haven't specified a specific combination of RID and framework. Alternatively it should probably just pick the first TFM/RID pair from the lock file. This is similar to how `dotnet run` works.
- Cleaned up the incremental build output formatting
- Use a single stream (output stream) since interleaving them was causing formatting issues (like losing random characters in the middle of outputting things).
- Didn't change how pack works, it still preserves the output structure when passing `--output`, this one is worth discussing. We could leave the build output inplace and only move the package to the output location. That's more consistent with how everything else works and can be a follow up PR.
