-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Update Arcade + Workloads #72947
Update Arcade + Workloads #72947
Conversation
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
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.
Can we do a test internal build of this?
Yes, I'm going to set one up since that's where it failed last time |
@@ -118,11 +118,6 @@ | |||
<PublishFlatContainer>true</PublishFlatContainer> | |||
</ItemsToPush> | |||
|
|||
<ItemsToPush Include="@(WorkloadsVSInsertionFile)"> |
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.
After this is removed, where do the assets from the swix projects get picked up for publishing?
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.
😢 good point. I should probably add the new zip files to the item group
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.
I think I fixed this. The zips are unique named, so we can just put them in the same folder
Approved pending the official build looking good. |
Publishing is fixed, but now it's looking for the individual files when signing that are no embedded inside a zip. @mmitche is there another way to lay out the files. The logs don't say where it's looking for the files, just that it can't find it under the artifacts. I suppose I can try to push the files individually and see if that works. |
@mmitche and I looked at a number of manifests from the internal builds against this branch. It appears all the artifacts are produced and everything should get signed like before. I'm not familiar with the runtime's tests that are failing. One seems to be related to Systerm.Data. Should I just try to rerun these? |
Rerunning the tests seem to work. @steveisok any idea who needs to sign off so we can merge this? |
@wtgodbe I assume we need to wait for branding changes before we can merge? |
Correct, this can be checked in after branding. @ericstj @ViktorHofer and @smasher164 will be handling merging runtime PRs will Carlos is OOF |
Update Arcade and the workloads project to leverage the new build tasks.
This also fixes the publishing issues we previously saw in the blob artifacts because of duplicate files. Instead, we'll create unique zip files per SDK featurebands for the workloads that will be used for creating the VSDROPs in dotnet-stage.