Skip to content

Update branding to 3.0.1 #14404

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Oct 1, 2019
Merged

Update branding to 3.0.1 #14404

merged 7 commits into from
Oct 1, 2019

Conversation

dougbu
Copy link
Contributor

@dougbu dougbu commented Sep 25, 2019

  • aspnet/AspNetCore-Internal#3153

@dougbu dougbu requested review from mmitche and a team September 25, 2019 02:09
@dougbu dougbu added the feature-platform Deprecated: Cross-cutting issues related to ASP.NET Core as a platform label Sep 25, 2019
- aspnet/AspNetCore-Internal#3153
- add `$(IgnorePackageBaselines)` property
- no changes in known frameworks, targeting pack features, et cetera
@dougbu dougbu force-pushed the dougbu/branding.3.0.1 branch from 03f3540 to 2d9d13a Compare September 25, 2019 22:49
@dougbu
Copy link
Contributor Author

dougbu commented Sep 26, 2019

F:\workspace\_work\1\s\src\Framework\ref\Microsoft.AspNetCore.App.Ref.csproj(177,5): error MSB3073: The command "tar -czf F:\workspace\_work\1\s\artifacts\installers\Release\aspnetcore-targeting-pack-3.0.1-ci.tar.gz ." exited with code 9009.

Either the targeting pack is not written anymore or its path changed. Both would be an unintended side effect of my changes.

@BrennanConroy
Copy link
Member

That's unrelated to this change. It's happening on a bunch of PRs. @JunTaoLuo and I think it might be an agent issue.

@@ -36,7 +36,8 @@
-->
<UseLatestPackageReferences Condition=" '$(UseLatestPackageReferences)' == '' AND '$(IsServicingBuild)' != 'true' ">true</UseLatestPackageReferences>
<UseLatestPackageReferences Condition=" '$(UseLatestPackageReferences)' == '' AND '$(IsImplementationProject)' != 'true' ">true</UseLatestPackageReferences>
<UseLatestPackageReferences Condition=" '$(UseLatestPackageReferences)' == '' AND '$(IsImplementationProject)' == 'true' AND ( '$(IsServicingBuild)' != 'true' OR '$(IsPackable)' == 'true' ) ">true</UseLatestPackageReferences>
<UseLatestPackageReferences
Condition=" '$(UseLatestPackageReferences)' == '' AND '$(IsImplementationProject)' == 'true' AND '$(IsPackable)' == 'true' ">true</UseLatestPackageReferences>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remaining changes in this file just address nits. Removed of '$(IsServicingBuild)' != 'true' OR because that's already checked 2 lines above.

@dougbu
Copy link
Contributor Author

dougbu commented Sep 26, 2019

@JunTaoLuo and I think it might be an agent issue.

Well, exit code 9009 means "file not found". If it's an agent issue, that would mean tar isn't found. @MattGal have the agents in NetCorePublic-Pool / BuildPool.Windows.10.Amd64.VS2019.Open moved to an older Windows build? (tar is now available by default but that's fairly recent.)

@BrennanConroy thanks, this makes more sense than my thought the targeting pack itself wasn't found. The command creates the .tar.gz file from files in its current directory.

- `$(IsServicingBuild)` disabled at the moment
@dougbu
Copy link
Contributor Author

dougbu commented Sep 27, 2019

This is ready to go once tar is found on the agents again

@dougbu
Copy link
Contributor Author

dougbu commented Sep 30, 2019

🆙📅 to include a more complete dotnet/core-eng#7970 workaround

  • may actually build this time 🤞

@@ -86,7 +86,7 @@
<TargetingPackInstallerBaseName>aspnetcore-targeting-pack</TargetingPackInstallerBaseName>

<!-- Used to only produce targeting pack installers/packages once per major.minor. -->
<IsTargetingPackBuilding Condition="'$(IsServicingBuild)' == 'true' AND '$(DotNetBuildFromSource)' != 'true'">false</IsTargetingPackBuilding>
<IsTargetingPackBuilding Condition="'$(AspNetCorePatchVersion)' == '0' AND '$(DotNetBuildFromSource)' != 'true'">false</IsTargetingPackBuilding>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm well, we need to rebuild the targeting pack in 3.0.1 so this logic needs some finessing. We need to be able to control whether the targeting pack builds. We can use this as a default logic though.

Copy link
Contributor

@JunTaoLuo JunTaoLuo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🥇 for coming up with a workaround to unblock us!

rm variable:global:_DotNetInstallDir -ea Ignore
rm variable:global:_ToolsetBuildProj -ea Ignore
rm variable:global:_MSBuildExe -ea Ignore
Remove-Item variable:global:_BuildTool -ea Ignore
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this change? Looks fine but I'm just curious.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because aliases are bad in scripts and VS Code warns about them

- work around dotnet/core-eng#7970
- install Git in repo if Tar can't be found in usual locations
- use found or installed Tar in Microsoft.AspNetCore.App.Ref project
  - copy into repo from wherever it's found
- add lots of `Write-Host` debugging

nit: clean up / comment on VS Code warnings about build.ps1
@dougbu dougbu force-pushed the dougbu/branding.3.0.1 branch from 611331a to f219a38 Compare September 30, 2019 23:06
@dougbu
Copy link
Contributor Author

dougbu commented Oct 1, 2019

Success modulo a missing New-Item -ItemType Directory .\.tools\ -ErrorAction SilentlyContinue ❕ ❕

@dougbu dougbu merged commit 6a50b16 into release/3.0 Oct 1, 2019
@ghost ghost deleted the dougbu/branding.3.0.1 branch October 1, 2019 04:07
@analogrelay analogrelay added this to the 3.0.1 milestone Nov 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-platform Deprecated: Cross-cutting issues related to ASP.NET Core as a platform
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants