Commit graph

13 commits

Author SHA1 Message Date
Přemek Vysoký
001d8e4465
[release/8.0.1xx] Fix internal VMR PR builds (#17208) 2023-08-17 17:27:03 +00:00
Přemek Vysoký
d4db076b20
Add VMR sync functionality into dotnet/dotnet's Codespaces (#15750) 2023-03-13 14:44:42 +01:00
Přemek Vysoký
a18c9247f4
Support sync of a single repository into the VMR (#15569) 2023-02-17 16:39:17 +00:00
Přemek Vysoký
0004325188
Turn on debugging output for VMR synchronization (#15524) 2023-02-13 11:43:27 +00:00
MilenaHristova
195977b515 add args to vmr sync 2023-02-08 13:44:25 +01:00
Přemek Vysoký
e5062aef44
Fix branch name in VMR CI (#15384) 2023-02-01 11:11:16 +00:00
Přemek Vysoký
83406a8660
Fix branch name in VMR CI (#15377)
The `Build.SourceBranchName` only gets the last segment, so for `release/8.0.xxx-preview1` it was `8.0.xxx-preview1` and the branch didn't get synchronized into the VMR.
2023-01-31 18:30:25 +01:00
dotnet-maestro[bot]
cd34038e97
[main] Update dependencies from dotnet/arcade-services (#15211)
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: Premek Vysoky <premek.vysoky@microsoft.com>
Co-authored-by: MilenaHristova <mhristova@microsoft.com>
2023-01-09 14:28:34 +01:00
Přemek Vysoký
0d24684503
Fix branch filters for the VMR synchronization (#15161) 2022-12-20 18:24:30 +00:00
Přemek Vysoký
ce1921c17d
Run VMR's pipelines from the VMR directly (#15124) 2022-12-15 09:33:09 +01:00
Přemek Vysoký
87955496af
Use VMR instead of the tarball for Source-Build builds (#15042)
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
2022-12-01 10:51:39 +01:00
Přemek Vysoký
1da909aef3
Fix hash of installer when preparing VMR synchronization (#14962) 2022-11-11 18:53:17 +00:00
Přemek Vysoký
6b20a1eae0
Add a VMR synchronization PR validation (#14918)
Adds a new pipeline that will run during installer's PRs that verifies that the current VMR tooling can synchronize that particular change into the VMR.
2022-11-08 16:47:32 +00:00