* add text-only packages to tarball
* add BuildTextOnlyPackages target to tarball build targets
* fix typo
* add content to text only package nuspec files
* Change reference to single nuspec file
* Update based on PR review
* prevent inner buildlog from being overwritten
* condition SourceBuildIntermediate.proj copy and build on the file not existing
* condition entire copy target on SourceBuildIntermediateProjTarget file existing
* Revert "condition entire copy target on SourceBuildIntermediateProjTarget file existing"
This reverts commit 995e106c81751b7d9597abf0c120963c2ab5374b.
* Revert "condition SourceBuildIntermediate.proj copy and build on the file not existing"
This reverts commit 3fbaa11bdb34cf9bb8f006f4c27bbd16783cac09.
* Revert "prevent inner buildlog from being overwritten"
This reverts commit f994e885fd7e0938dcc80150f3a0a8aad215f014.
Co-authored-by: dseefeld <dseefeld@microsoft.com>
* Tweaks for RTM stable building and servicing
- When building from source offline in a stable configuration, the shared frameworks versions will match the directory from which the runtime archives are located in, both stable. This is in contrast to when not building from source, in which the runtime archives will appear in non-stable directories.
- The targeting pack versions should not be assumed to always match the runtime framework versions, and the blob directories containing them are the same. Add new dependencies so that we can track where the targeting pack directory is over time.
- PGO archives coming from runtime are always built non-stable. This means the download location needs to be tweaks, and crossgen calls need to look for shared framework binaries in the non-stable locations.
- For source-build, the templating should move to a new non-stable dependency. This is used to determine the version of the source build intermediate package.
* Generate the full nuget version in the source build tarball job.
The source build tarball job needs the full nuget version so that it can publish the blob to the right location (`Sdk/<full version>/source-<stable version>.zip). This involves being able to call the GenerateFullNuGetVersion target and the targets it depends on.
* Copy instead of clone and remove .git/objects directories
* Add depth 1 to fetch command
* Add commit count to git-info for installer repo
* Update targets to fix dependency ordering
Some repos take a dependency on PrepareInnerSourceBuildRepoRoot,
assuming that the inner repo will be setup. The condition for copy
instead of clone caused a conflict.
Keep PrepareInnerSourceBuildRepoRoot and make it depend on
either copy or clone completing.
* Don't copy artifacts dir
* Actually don't remove artifacts directory
* Update prebuilt version
* [ArPow] Add runtime repo to tarball (#11506)
* Add runtime repo / update runtime project
* Update runtime-portable logs and properties
* Create runtime-portable git-info
* Fix unpack of IntermediatePackages
* Re-enable references to runtime
* Pass TargetRid and NonPortable to runtime build
* Only build allconfigurations in non-portable build
* Add SDK patch to disable new CA warning
* Increase built tarball timeout
* Update prebuilt version
* [ArPow] Add installer repo to tarball (#11483)
* Ignore failure in no-network case
Co-authored-by: Dan Seefeldt <dseefeld@microsoft.com>
Co-authored-by: Michael Simons <msimons@microsoft.com>
Co-authored-by: Matt Galbraith <mattgal@microsoft.com>
* Update SBRP to get version with updated ilasm
Also, remove the prebuilts for packages that weren't being built
correctly.
* Add empty prebuilt directory
* Add some needed prebuilt packages to override temporarily bad ref packages.
* Remove bad ref packages.
* Also don't copy new versions of the bad SBRP packages after the SBRP build.
* Account for missing intermediate packages and different paths.
* Address code review comment.
* Initial checkin of source-build tarball build infra
* Add a couple more comments
* Update eng/SourceBuild.Version.Details.xml based on PR review
Co-authored-by: Chris Rummel <crummel@microsoft.com>
* Updates based on PR review comments
Co-authored-by: Chris Rummel <crummel@microsoft.com>
