Skip to content

Conversation

@marcpopMSFT
Copy link
Member

  • Please add description for changes you are making.
  • If there is an issue related to this PR, please add the reference.

marcpopMSFT and others added 17 commits February 6, 2022 09:41
…ence-packages build 20220205.1 (#13179)

[release/6.0.1xx] Update dependencies from dotnet/source-build-reference-packages
…ild in Roslyn (#13093)

* override SDK for Microsoft.Net.Sdk.WindowsDesktop references in roslyn

* add new EmptySdk in the source build tarball

* remove roslyn solution filter patch
…207.2 (#13186)

Microsoft.DotNet.CMake.Sdk , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Arcade.Sdk
 From Version 6.0.0-beta.22102.3 -> To Version 6.0.0-beta.22107.2

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
[release/6.0.1xx] Windows SDK projection update
…-2022-02-08-1019

Merging internal commits for release/6.0.1xx
…ence-packages build 20220210.1 (#13215)

[release/6.0.1xx] Update dependencies from dotnet/source-build-reference-packages
…ence-packages build 20220215.1 (#13229)

[release/6.0.1xx] Update dependencies from dotnet/source-build-reference-packages
@marcpopMSFT
Copy link
Member Author

@MichaelSimons , should I continue to expect significant changes for source build in the 1xx branch? For 5.0 servicing we didn't auto-merge other than N-1 to main but it seems like with 6.0, there have been a lot of 1xx changes (and potentially .2xx changes) which are requiring manual merging.

@MichaelSimons
Copy link
Member

@MichaelSimons , should I continue to expect significant changes for source build in the 1xx branch? For 5.0 servicing we didn't auto-merge other than N-1 to main but it seems like with 6.0, there have been a lot of 1xx changes (and potentially .2xx changes) which are requiring manual merging.

Yes, source-build has traditionally only supported the oldest sdk channel per agreement with our SB partners. We would like to get to the point where we support all channels but don't have the resources to support that at the moment. The primary changes being made in 1xx is all related to testing and eng infra to automate the release process. I expect this will slow down drastically in a couple more servicing releases but there will still be occasional changes needed.

@marcpopMSFT
Copy link
Member Author

@MichaelSimons if ya'll are going to focus on the oldest but the SDK teams are focused on the newest, do you think you'd be able to pick up owning the manual merge forward or should we enable auto-merge forward?

@MichaelSimons
Copy link
Member

Please enable auto-merge forward.

@marcpopMSFT
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@marcpopMSFT
Copy link
Member Author

@MichaelSimons Any suggestions on this tarbal failure:

/tarball/src/roslyn.592501cbb9c9394072a245c15b3458ff88155d85/artifacts/source-build/self/src/src/Scripting/CSharp/Microsoft.CodeAnalysis.CSharp.Scripting.csproj : error NU1102: Unable to find package Microsoft.CSharp with version (>= 4.7.0) [/tarball/src/roslyn.592501cbb9c9394072a245c15b3458ff88155d85/artifacts/source-build/self/src/Roslyn.sln]

@MichaelSimons
Copy link
Member

@marcpopMSFT - I opened dotnet/source-build#2783 to track the underlying issue. Feel free to merge. The fix will flow in from dotnet/source-build-reference-packages

@MichaelSimons
Copy link
Member

Thinking about this more, I will fix the issue right away and update this PR.

…ence-packages build 20220303.2

Microsoft.SourceBuild.Intermediate.source-build-reference-packages
 From Version 6.0.0-servicing.22151.1 -> To Version 6.0.0-servicing.22153.2
@MichaelSimons
Copy link
Member

I cherry-picked the fix for the tarball failure.

@MichaelSimons MichaelSimons merged commit c3da28f into release/6.0.2xx Mar 5, 2022
@MichaelSimons MichaelSimons deleted the marcpopMSFT-catchup60200-1 branch March 5, 2022 02:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants