Currently VSTS is producing duplicate package and they are running into
each other will producing
Today:
Linux x64 build definition: both .deb and .tar.gz
Ubuntu 16.04 build definition: both .deb and .tar.gz (ex.
dotnet-sdk-2.0.0-preview3-006477-linux-x64.tar.gz,
dotnet-sdk-debug-2.0.0-preview3-006477-linux-x64.tar.gz,
dotnet-sdk-internal-2.0.0-preview3-006477-linux-x64.tar.gz)
After this change:
Linux x64: .tar.gz
Ubuntu 16.04: .deb
No change for windows and macOS
Tested on Ubuntu with and without --linux-portable and windows
* dotnet/release/2.0.0: (72 commits)
Updating the signing project to reflect the new location of the resolver.
Another update to MSBuild. To 15.3.0-preview-000385-01.
Another update to msbuild. To 15.3.0-preview-000385-01.
Update to SetupCrossgen 183 - Coherence 25615
Don't include .NET Core MS.NET.Build.Extensions tasks for .NET Framework and vice versa
Update version of SDK and MS.NET.Build.Extensions, adapt to layout change
Updating MSBuild to 15.3.0-preview-000384-01
Update MSBuild to 15.3.0-preview-000384-01
test pack command
Changing NuGet version to Preview3-4154
Updating NuGet version to Preview3-4154
Add Microsoft.NET.Build.Extensions files to package for VS insertion
reenable smoke test of F# templates
empty commit
Don't try to CrossGen .NET Framework support DLLs
Update test platform to 15.3.0-preview-20170609-02.
Turning off implicit restore when publishing the build project.
Updating the vstest.console to use the same runtime that is shipping with the CLI.
Update to template build 256 to fix Web Auth scenarios
Add test for consuming .NET Standard 2.0 library from .NET Framework 4.6.1 project
...
* release/2.0.0: (104 commits)
Updating NuGet.
Remove redundant error handling from project provider, add a better message for deserialization exceptions
Temporarily change the runtime deb pkg name to unblock the integration.
insert new bits of TestPlatform which has bug fixes.
Add missing using directive
Only catch JsonException in the method that dispatches to the appropriate handlers
Shorten names a bit more, make project names match folder names
Shorten test project names
Fix flow from the refactoring
Remove NuGet.Configs, add inversion of the launch profile flag, move profile application logic to its own method
Make errors more specific, add support for setting the launch URL for ASP.NET apps
Add missed launch settings, fix NuGet.configs, remove unused packages
Ad tests, fix issue where profile not found isn't an error
Initial add of launchSettings.json support
Update to SetupCrossgen 134 - Coherence 25332
Fix dotnet-deb-tool path.
Update dotnet-deb-tool to 2.0.0-preview2-25331-01
Shorten names a bit more, make project names match folder names
Shorten test project names
Re-enable telemetry for new
...
Our build scripts were pulling down all of buildtools and run.exe in
service of "clean.{cmd|sh}". While having consisent commands across
the repos is a good thing to strive for, we are pulling down a bunch
of additional stuff we don't need for simple commands that have well
known analogs (e.g. git clean).
If we had been all in on run.exe, this might have made sense, but we
aren't, so it feels like something we should clean up.
By doing this, we can stop downloading bootstrap from github when we
build (super dangerous anyway because changes in buildtools could have
broken us).
In addition, I changed the way we install dotnet to just invoke the
script in `scripts/obtain/` instead of downloading a version from
GitHub. This makes local development of changes to obtain easier and
removes yet another place we had to download a script.
The parameter passed to `exit` was always 0 (exit code of previous `echo` call). It seems to me that the intention is to terminate the script with the actual exit error code (!= 0).
When trying to cross build, Rid needs to change to the target Rid,
but architecture should use x64 as it as host.
In addition to the existing --architecture option, and additional --runtime-id option is required.
It duplicates functionality achieved by using `--runtime-id linux-x64`.
Remove it and fix callers.
Keep the the --linux-portable flag in the build scripts; that now calls
--runtime-id linux-x64 in the install script.
* Add support to build with the linux portable
* Pass targets to run for the linux portable
* Address PR comments
* Update the bootstrapper version
* Address the PR comments for improving the help text
* Fixing permissions
* Allow host info passed in from the command line to override machine settings
* Simplify the logic
* Address PR comments to keep a separate HostRid and HostOSName that are static
* Rename to BuildInfo.props
* Address PR comments
* Fix the previous merge
* Fix spacing
* Address PR comments
During the cli build, the cli downloads and executes the bootstrap
script from buildtools. The bootstrap script then downloads and executes
the dotnet-install script from cli, but in the 'rel/1.0.0' branch, not
the master branch.
This means that someone building cli's master branch will end up using
the dotnet-install.sh or dotnet-install.ps1 script from cli's rel/1.0.0
branch.
Fix that by telling the bootstrap script to download and use the version
of dotnet-install script from the master branch (which is the current
branch the user is building).
Ideally, we would just call the dotnet-install script in the current
repo/branch, but because the bootstrap script sits in the middle and is
part of a different repository, we can't.
This is a workaround for #5410.
Works around NuGet parallel restore timeouts becoming build failures when the machine has a slow connection, for example in our Docker Fedora containers.
* Switch to using new bootstrap script to initialize buildtools.
* Set up the version-specific shared runtime symlink in run-build so buildtools doesn't have to care about it.
* Address code review feedback.
* Addressed code review feedback.
* Change to using bootstrap script for Linux build as well.
* Change to using latest for CLI.
