Skip to content
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

Merged
merged 4 commits into from
Aug 5, 2022
Merged

Update Arcade + Workloads #72947

merged 4 commits into from
Aug 5, 2022

Conversation

joeloff
Copy link
Member

@joeloff joeloff commented Jul 27, 2022

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.

@dotnet-issue-labeler
Copy link

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.

@ghost ghost assigned joeloff Jul 27, 2022
@joeloff joeloff requested review from wtgodbe and directhex July 27, 2022 16:25
Copy link
Member

@wtgodbe wtgodbe left a 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?

@joeloff
Copy link
Member Author

joeloff commented Jul 27, 2022

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)">
Copy link
Member

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?

Copy link
Member Author

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

Copy link
Member Author

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

@mmitche
Copy link
Member

mmitche commented Jul 27, 2022

Approved pending the official build looking good.

@joeloff
Copy link
Member Author

joeloff commented Jul 27, 2022

Approved pending the official build looking good.

It seems to be working:
image

@joeloff
Copy link
Member Author

joeloff commented Jul 28, 2022

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.

@joeloff
Copy link
Member Author

joeloff commented Jul 29, 2022

@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?

@mmitche
Copy link
Member

mmitche commented Jul 29, 2022

I'm not familiar with the failures, but the build analysis indicates that these are failing in release/6.0:

image

Do have another internal build for one last check?

@joeloff
Copy link
Member Author

joeloff commented Aug 1, 2022

Rerunning the tests seem to work. @steveisok any idea who needs to sign off so we can merge this?

@joeloff
Copy link
Member Author

joeloff commented Aug 1, 2022

@wtgodbe I assume we need to wait for branding changes before we can merge?

@wtgodbe
Copy link
Member

wtgodbe commented Aug 1, 2022

Correct, this can be checked in after branding. @ericstj @ViktorHofer and @smasher164 will be handling merging runtime PRs will Carlos is OOF

@steveisok steveisok self-requested a review August 2, 2022 00:54
@steveisok steveisok merged commit edd35c5 into dotnet:release/6.0 Aug 5, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Sep 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants