-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Attempt to auto-publish vs.redist packages to orchestrated feed #20211
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
Conversation
@@ -276,6 +280,10 @@ | |||
ManifestArtifactData="NonShipping=true" | |||
Condition="'%(PackageToPublish.Category)' != 'ship'" /> | |||
|
|||
<PackageToPublishToTransport |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PublishToTransportFeed
is the target that runs when we're trying to publish to the orchestrated feed, so as long as I also update https://devdiv.visualstudio.com/DevDiv/_git/DotNet-Orchestration-Utilities?path=%2Fsrc%2FFinal.VSFeedPublish.targets&version=GBmaster, the orchestration should take care of copying the redist packages from the orchestrated feed to the VS feed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another option would be to include these packages in @(FilesToPublish)
i.e. changing the input GetFilesToPublish
target. That has the advantage of placing the files in the \aspnetci drop too.
This doesn't yet solve the issue of giving the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks reasonable to me!
I think this should also use non-stable versioning for the vs.redist package now without destabilizing anything else, but I'm not 100% sure because I haven't been able to successfully build locally yet 😆 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good modulo one typo. Fire up a build on TeamCity if you wanna test it out -- publish attempts shouldn't hurt anything.
Unless you've updated the TC configuration to skip publishing for non-ProdCon builds, any build should do. And, if you did change the configuration, can temporarily change it back to be unconditional 😃 |
Don't I need to provide some variables that would normally come from orchestration (e.g. the key for |
Ah, you want to test to a later endpoint than I thought. I was just looking to see what the build tried to push. |
Well, that might be enough - I'll try queuing a team city build just in case |
I don't see a way to run a build against a custom branch in TeamCity 😦 |
I could merge this then revert it, and run a build against the initial merge |
@JunTaoLuo helped me figure out how to change the branch, so I've got the build running now |
@@ -276,6 +280,10 @@ | |||
ManifestArtifactData="NonShipping=true" | |||
Condition="'%(PackageToPublish.Category)' != 'ship'" /> | |||
|
|||
<PackageToPublishToTransport |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another option would be to include these packages in @(FilesToPublish)
i.e. changing the input GetFilesToPublish
target. That has the advantage of placing the files in the \aspnetci drop too.
- should trigger a build that's more likely to succeed
The build succeeded, but didn't attempt to publish the redist packages because it didn't pass |
Here's the Dotnet-Orchestration-Utilities PR, @dagood PTAL: https://devdiv.visualstudio.com/DevDiv/_git/DotNet-Orchestration-Utilities/pullrequest/238164?_a=overview |
…/aspnetcore into wtgodbe/AutoPublishRedist
Build failed before it could be informative because we didn't pass the account name or key for the orchestrated feed. Instead I'm gonna just print what we would try to publish in the next build (I'll undo 3a5b333 before merging) |
@dougbu I have some concern about using |
Looks like the outage is impacting my val build 😢 hopefully it's fixed soon, or at least by monday |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Not working yet, the redist packages aren't being included in |
build/Publish.targets
Outdated
@@ -174,6 +175,10 @@ | |||
<PackageToPublish Include="%(_SymbolsPackageArtifactInfo.ArtifactPath)" Category="symbols" IsSymbolsPackage="true" /> | |||
</ItemGroup> | |||
|
|||
<ItemGroup> | |||
<RedistPackageToPublish Include="$(DependencyAssetsDir)(SharedFrameworkRedistPackageId)*" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well don't I have an egg on my face... This isn't working because there's no '$' before (SharedFrameworkRedistPackageId)
🤦♂
Ok, this should be ready for review - the most recent TeamCity build confirmed it would attempt to publish the redist packages (w/ non-stable versions):
|
@dougbu @JunTaoLuo any last concerns? |
I believe I've reset everything in teamcity to the way it was (I only changed VCSBranches & IsFinalBuild), but it'd be great if you guys could take a glance at the project settings to see if it looks like I missed anything |
You can double-check things too. Compare the public and private build configurations and confirm the only differences are obvious eg. related to signing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Smallish bits to change before merging…
…/aspnetcore into wtgodbe/AutoPublishRedist
@dougbu I pushed a commit responding to your feedback |
Doing that now |
Attempts to resolve https://github.com/dotnet/aspnetcore-internal/issues/3387
@mmitche is there a way I can run a test prodcon build of AspNetCore 2.1 to see if this works?
TODO: update https://devdiv.visualstudio.com/DevDiv/_git/DotNet-Orchestration-Utilities?path=%2Fsrc%2FFinal.VSFeedPublish.targets&version=GBmaster