Age | Commit message (Collapse) | Author |
|
|
|
We need the latest compatibility mappings for NuGet but the CLI hasn't
yet picked up a new NuGet drop.
Workaround this by manually patching the NuGet.Frameworks.dll in CLI.
|
|
* Upgrade CLI, buildtools for RTM shared framework.
* Upgrade buildtools, add new platforms to init-tools (ubuntu 16.10, fedora 24, opensuse 42.1).
|
|
|
|
output (#11059)
* Enable option to suppress non-error output from the console output for
init-tools.
* Redirect standard output to log
* Remove unneccesary arg
* Add Linux init-tools changes
* revert dotnet to x64
* Remove echo line from run.sh
|
|
|
|
This lets us publish a package and consume it immediately from our
builds.
Without this our CI clients were relying on an HTTP cache of our myget
feeds and failing when we updated projects or buildtools.
|
|
Before this change, a failure fairly early in the `init-tools.sh` process could result in subsequent attempts being short-circuited.
This introduces a marker file that is only written at the very end of the script, so that a `dotnet restore` or `init-tools.sh`-from-package failure can be retried immediately.
|
|
* Also, fall back to Ubuntu 14.04 if using an unsupported version.
|
|
With the updated buildtools, we should now be able to build on all the supported distros:
- Centos 7
- Fedora 23
- openSUSE 13.2
- RHEL 7.2
- Ubuntu 14.04
- Ubuntu 16.06
Since the CLI support for some of these is still comming online, I
have published custom versions to our own Azure Blob storage that we
can download. Once CLI has real builds ready, we can move back to
their built binaries.
I also cleaned up how we compute the RID for the tools to restore.
|
|
The layout of CLI has changed and the logic resulted in a non working
CLI and errors during init-tools.sh
|
|
Downloading from Azure can transiently fail for a number of reasons. Add
some retry logic when downloading to avoid transient failures. For *nix
variants add a retry value when using curl (wget retries by default).
|
|
Clean up all non-essential references to DNXCore50.
|
|
|
|
|
|
|
|
|
|
Include capitalization fixes for NETNative packages to avoid xplat nuget race condition.
|
|
|
|
|
|
The CoreFx build using build.sh is currently broken on CentOS because it
doesn't restore the right version of the .NET CLI. This change fixes
that and also restores the appropriate version for Debian and RHEL, and
sets appropriate defaults for TestNugetRuntimeId for those three
platforms.
It also makes a few other minor edits:
- Remove ToolNugetRuntimeId, which is no longer used.
- Don't use "sh" when invoking init-tools.sh, because Bash is needed to
use the "source" command.
- Add a few more console output messages to init-tools.sh, similar to
the ones already in init-tools.cmd.
- Fix indentation in init-tools.sh.
- Set the default TestNugetRuntimeId in build.sh when the target OS is
specified to be FreeBSD, NetBSD, or Windows.
|
|
- We have moved our feeds to our enterprise myget
account (dotnet.myget.org). Start pulling from there and use the v3
feeds since we are restoring with tools that understand them.
- Remove some no longer needed NuGet commands and sources
|
|
|
|
|
|
|
|
|
|
Respect BUILDTOOLS_OVERRIDE_RUNTIME in init-tools.
|
|
While we would like to use 'Latest' as the version for dogfooding
purposes, we have to keep our builds unblocked and there is currently
a breaking change we have to react to. So to unblock we are fixing
to a particular version we know works.
|
|
If the user has specified a value for BUILDTOOLS_OVERRIDE_RUNTIME
(e.g. if they are building on an OS or distro for which a package
is not available), copy the specified runtime into the necessary
locations for dotnet, dnx, etc.
|
|
|
|
[tfs-changeset: 1562939]
|