For PRs, the Source-Build leg that was running inside of the Build stage is now moved to a separate stage but runs more or less the same: https://dev.azure.com/dnceng-public/public/_build/results?buildId=97509&view=results
Instead of creating the tarball, we are building the `dotnet/dotnet` repo there.
For internal rolling builds, we are taking [this pipeline](https://dev.azure.com/dnceng/internal/_build/results?buildId=2056327&view=results) and merging it into `dotnet-installer-official-ci`.
So it's one extra stage that runs pretty quick (faster than the Build stage by far).
It won't be creating and pushing the tarball artifact anymore though.
Once the rolling build is finished, there won't be no more source-build-build pipeline but instead dotnet-dotnet-official-ci which will build the dotnet/dotnet repo again instead of the tarball that was originally produced from the rolling build.
The MSFT SDK from the installer build will still be consumed by it though.
More details https://github.com/dotnet/arcade/issues/10677
Source-build 7.0.0 created these packages with an incorrect version number which is stuckthe previously-source-built PVP for the 7.0.1 release. This causes a problem if bootstapping because the Microsoft versions of these packages don't actually exist, so trying to download them fails. This change allows us to override the version read out of PVP and set it to the actual version used by runtime.
* Add CI for dotnet-security-partners
Remove nuget configs from all repo submodules
Address code review
Move security-partners ci to tarball/eng dir
Copy out installer NuGet config before build
Fix relative path for installer template
Switch to 20.04 image
* Add nuget-client patch to avoid nuget security scan errors
* Revert "Add nuget-client patch to avoid nuget security scan errors"
This reverts commit 6eca00a41813171019b24597386a9074e2faa07b.
* Remove NuGet.config workaround for security-partners ci
* Rename MicrosoftAspNetCoreAppRuntimePackageVersion so existing Artifacts tarballs don't override it,
and stop adding it to the PackageVersions.props in new Artifacts tarballs.
* Patch PreviouslySourceBuiltPackageVersions.
* PR feedback.
* Enabled source-building with mono runtime on any architecture.
Adds an argument to the top-level build script to use the mono
runtime, and sets the flags needed for the different repos
to work with mono.
* Sync with sdk patch.
* Remove patches.
* PR feedback.
* Adding ppc64le arch for source build (#14631)
* Remove llvm-project from source-build as we have removed this dependency in runtime. (#14697)
* Remove llvm-project from source-build as we have removed this dependency in runtime.
* Add patch for the backport PR to get this to build for now.
* Remove unneeded copy of this patch.
* [release/7.0.1xx] Update dependencies from dotnet/sdk (#14705)
[release/7.0.1xx] Update dependencies from dotnet/sdk
- Remove backported command-line-api patch
* Don't use the MSBuild server process for init-build.proj. (#14643)
* Don't use the MSBuild server process for init-build.proj.
This appears to fix an issue where our SdkResolver is not loaded because there are still lingering dotnet processes when we try to binplace the resolver DLL.
* Address code review feedback.
* Update patch backport comments and remove obsolete patch (#14710)
* [release/7.0.1xx] .NET Source-Build 7.0.100-rc.2 October 2022 Updates (#14728)
* Update source-build to 7.0 RC2
* Also update tarball global.json
* Don't touch root global.json in case it is managed by automation
* Add back source-build patch that is still required in this branch
Co-authored-by: Swapnali911 <Swapnali.Pawar1@ibm.com>
Co-authored-by: Chris Rummel <crummel@microsoft.com>
Co-authored-by: dotnet-maestro[bot] <42748379+dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: Michael Simons <msimons@microsoft.com>
Co-authored-by: Logan Bussell <loganbussell@microsoft.com>
Co-authored-by: Jason Zhai <v-wuzhai@microsoft.com>
