Move src/SourceBuild/tarball/* up one folder (#15166)

This commit is contained in:
Přemek Vysoký 2022-12-21 21:47:54 +01:00 committed by GitHub
parent 118280814f
commit 5aac0db522
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
159 changed files with 12 additions and 11 deletions

View file

@ -373,11 +373,12 @@ stages:
# the VMR synchronization step is run to validate that the PR can be merged and later # the VMR synchronization step is run to validate that the PR can be merged and later
# synchronized into the VMR without problems. # synchronized into the VMR without problems.
# You can do this by allowing the Synchronize_VMR stage from above in PRs. # You can do this by allowing the Synchronize_VMR stage from above in PRs.
- ${{ if eq(variables['Build.Reason'], 'PullRequest') }}: # TODO - Temporarily disabled (https://github.com/dotnet/source-build/issues/3184)
- template: eng/pipelines/templates/stages/vmr-build.yml # - ${{ if eq(variables['Build.Reason'], 'PullRequest') }}:
parameters: # - template: eng/pipelines/templates/stages/vmr-build.yml
vmrBranch: ${{ parameters.vmrBranch }} # parameters:
isBuiltFromVmr: false # vmrBranch: ${{ parameters.vmrBranch }}
# isBuiltFromVmr: false
- ${{ if and(ne(variables['System.TeamProject'], 'public'), notin(variables['Build.Reason'], 'PullRequest')) }}: - ${{ if and(ne(variables['System.TeamProject'], 'public'), notin(variables['Build.Reason'], 'PullRequest')) }}:
- stage: Publish - stage: Publish

View file

@ -22,7 +22,7 @@
### ###
### The whole process can be reproduced locally easily by running this script. ### The whole process can be reproduced locally easily by running this script.
### The patches are located in a folder in the 'dotnet/installer' repository. ### The patches are located in a folder in the 'dotnet/installer' repository.
### At the moment of writing, the location is 'src/SourceBuild/tarball/patches' but to get ### At the moment of writing, the location is 'src/SourceBuild/patches' but to get
### the up-to-date location, please see the 'patchesPath' property in ### the up-to-date location, please see the 'patchesPath' property in
### https://github.com/dotnet/dotnet/blob/main/src/source-mappings.json ### https://github.com/dotnet/dotnet/blob/main/src/source-mappings.json
### ###

View file

@ -44,7 +44,7 @@ git format-patch --zero-commit --no-signature -1
``` ```
Then, move the patch file into this repo, at Then, move the patch file into this repo, at
`src/SourceBuild/tarball/patches/<repo>`. `src/SourceBuild/patches/<repo>`.
> If you define `PATCH_DIR` to point at the `patches` directory, you can use > If you define `PATCH_DIR` to point at the `patches` directory, you can use
> `-o` to place the patch file directly in the right directory: > `-o` to place the patch file directly in the right directory:

View file

@ -10,7 +10,7 @@ What this means:
In the VMR, you can find: In the VMR, you can find:
- source files of [each product repository](#list-of-components) which are mirrored inside of their respective directories under [`src/`](https://github.com/dotnet/dotnet/tree/main/src), - source files of [each product repository](#list-of-components) which are mirrored inside of their respective directories under [`src/`](https://github.com/dotnet/dotnet/tree/main/src),
- tooling that enables [building the whole .NET product from source](https://github.com/dotnet/source-build) on Linux platforms, - tooling that enables [building the whole .NET product from source](https://github.com/dotnet/source-build) on Linux platforms,
- small customizations, in the form of [patches](https://github.com/dotnet/dotnet/tree/main/src/installer/src/SourceBuild/tarball/patches), applied on top of the original code to make the build possible, - small customizations, in the form of [patches](https://github.com/dotnet/dotnet/tree/main/src/installer/src/SourceBuild/patches), applied on top of the original code to make the build possible,
- *[in future]* E2E tests for the whole .NET product. - *[in future]* E2E tests for the whole .NET product.
Just like the development repositories, the VMR will have a release branch for every feature band (e.g. `release/8.0.1xx-preview1`). Just like the development repositories, the VMR will have a release branch for every feature band (e.g. `release/8.0.1xx-preview1`).

Some files were not shown because too many files have changed in this diff Show more