Skip to content

Conversation

dotnet-maestro-bot
Copy link
Contributor

I detected changes in the vs17.0 branch which have not been merged yet to main. I'm a robot and am configured to help you automatically keep main up to date, so I've opened this PR.

This PR merges commits made on vs17.0 by the following committers:

Instructions for merging from UI

This PR will not be auto-merged. When pull request checks pass, complete this PR by creating a merge commit, not a squash or rebase commit.

merge button instructions

If this repo does not allow creating merge commits from the GitHub UI, use command line instructions.

Instructions for merging via command line

Run these commands to merge this pull request from the command line.

git fetch
git checkout vs17.0
git pull --ff-only
git checkout main
git pull --ff-only
git merge --no-ff vs17.0

# If there are merge conflicts, resolve them and then run git merge --continue to complete the merge
# Pushing the changes to the PR branch will re-trigger PR validation.
git push https://github.com/dotnet-maestro-bot/msbuild HEAD:merge/vs17.0-to-main
or if you are using SSH
git push [email protected]:dotnet-maestro-bot/msbuild HEAD:merge/vs17.0-to-main

After PR checks are complete push the branch

git push

Instructions for resolving conflicts

⚠️ If there are merge conflicts, you will need to resolve them manually before merging. You can do this using GitHub or using the command line.

Instructions for updating this pull request

Contributors to this repo have permission update this pull request by pushing to the branch 'merge/vs17.0-to-main'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.

git checkout -b merge/vs17.0-to-main main
git pull https://github.com/dotnet-maestro-bot/msbuild merge/vs17.0-to-main
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet-maestro-bot/msbuild HEAD:merge/vs17.0-to-main
or if you are using SSH
git checkout -b merge/vs17.0-to-main main
git pull [email protected]:dotnet-maestro-bot/msbuild merge/vs17.0-to-main
(make changes)
git commit -m "Updated PR with my changes"
git push [email protected]:dotnet-maestro-bot/msbuild HEAD:merge/vs17.0-to-main

Contact .NET Core Engineering if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/master/scripts/GitHubMergeBranches.ps1.

dotnet-maestro bot and others added 9 commits September 9, 2021 09:32
…908.11 (dotnet#6833)

Microsoft.DotNet.Arcade.Sdk
 From Version 5.0.0-beta.21427.7 -> To Version 5.0.0-beta.21458.11
Fixes #dotnet#6576

### Context
dotnet#6576 revealed that the `.copycomplete` file marker is updated even when the `Copy` task in `_GetCopyFilesMarkedLocal` doesn't _actually_ copy anything. This can mess with incremental builds.

### Changes Made
This change adds an output parameter, `CopiedAtLeastOneFile` to the `Copy` task that the `Touch` task is now conditioned off of.

### Testing
Tested local builds

### Notes
This could also be done by having an ITaskItem[] that contains all files that were actually copied. Then the touch task could check if that item were empty. I opted for the straightforward route since the ITaskItem[] solution isn't needed yet, and this implementation can easily be changed when we do need that.

Co-authored-by: Forgind <[email protected]>
…914.1 (dotnet#6850)

Microsoft.DotNet.Arcade.Sdk
 From Version 5.0.0-beta.21458.11 -> To Version 5.0.0-beta.21464.1

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
* Update to SDK 5.0.401

Avoids NuGet signing issues and is generally newer and better.

* Update eng\Versions.props

* Update NuGetBuildTasksVersion in eng\Versions.props

Co-authored-by: Ladi Prosek <[email protected]>
Skip Updating CopyComplete Marker When Not Necessary
Microsoft.DotNet.Arcade.Sdk
 From Version 5.0.0-beta.21464.1 -> To Version 5.0.0-beta.21505.11
Fixes dotnet#6917 by ensuring that the copy-marker file is _always_ added
to the FileWrites item if the copy-referenced-assemblies target runs
so that IncrementalClean never sees it as an 'orphan' file and then
deletes it.
@ladipro ladipro added the merge-when-branch-open PRs that are approved, except that there is a problem that means we are not merging stuff right now. label Oct 14, 2021
@ladipro
Copy link
Member

ladipro commented Oct 14, 2021

@rainersigwald just saw your comment on #6866. It's the same backport so I'll wait for you.

@ladipro ladipro removed the merge-when-branch-open PRs that are approved, except that there is a problem that means we are not merging stuff right now. label Oct 14, 2021
@rainersigwald
Copy link
Member

While we're still waiting for Tactics approval on this for 16.11 and 17.0 I think we must fix it for 17.1, so I think we can go ahead. As long as we merge, rather than squashing, I don't think we'll lose anything if Tactics for some reason doesn't approve.

@ladipro ladipro added the merge-when-branch-open PRs that are approved, except that there is a problem that means we are not merging stuff right now. label Oct 14, 2021
These assemblies have moved and versioned in Visual Studio 2022.

Update of the workaround for dotnet#1675 in dotnet#4139.
@dotnet-maestro-bot
Copy link
Contributor Author

This pull request has been updated.

This PR merges commits made on vs17.0 by the following committers:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge-when-branch-open PRs that are approved, except that there is a problem that means we are not merging stuff right now.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants