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

[ci] Set OfficialBuildId when building asset manifests #23102

Merged
merged 1 commit into from
Jun 21, 2024

Conversation

pjcollins
Copy link
Member

Context: 812807c

The maestro build promotion step has been failing with:

PublishArtifactsInManifest.proj(130,5): error : Asset 'D:\a\_work\1\a\3fecf55a-18fb-414d-b980-84c0f56a3856\MergedManifest.xml' already exists with different contents at 'https://dotnetbuilds.blob.core.windows.net/public/assets/manifests/dotnet-maui/9.0.0-ci-dev/MergedManifest.xml'

The manifest version information passed to the PublishBuildAssets.proj
build does not contain revision information, causing asset publishing
to fail as it will not overwrite existing assets with the same version.

We should be able to fix this by setting the OfficialBuildId property
when building the asset manifests, similar to what is currently being
done when packing the NuGets.

@pjcollins pjcollins requested a review from a team as a code owner June 17, 2024 22:10
@PureWeen PureWeen added the area-infrastructure CI, Maestro / Coherency, upstream dependencies/versions label Jun 20, 2024
@PureWeen
Copy link
Member

/rebase

Context: 812807c

The maestro build promotion step has been failing with:

    PublishArtifactsInManifest.proj(130,5): error : Asset 'D:\a\_work\1\a\3fecf55a-18fb-414d-b980-84c0f56a3856\MergedManifest.xml' already exists with different contents at 'https://dotnetbuilds.blob.core.windows.net/public/assets/manifests/dotnet-maui/9.0.0-ci-dev/MergedManifest.xml'

The manifest version information passed to the `PublishBuildAssets.proj`
build does not contain revision information, causing asset publishing
to fail as it will not overwrite existing assets with the same version.

We should be able to fix this by setting the `OfficialBuildId` property
when building the asset manifests, similar to what is currently being
done when [packing the NuGets][0].

[0]: https://github.com/dotnet/maui/blob/5d3e788f297098417f6c603e5187fb24a37dda63/eng/cake/dotnet.cake#L285
@github-actions github-actions bot force-pushed the dev/pjc/net9-maestro-vers branch from 838eb45 to ed9b270 Compare June 20, 2024 09:32
@PureWeen PureWeen requested review from rmarinho and removed request for Eilon and StephaneDelcroix June 21, 2024 16:29
@PureWeen PureWeen enabled auto-merge (squash) June 21, 2024 16:38
@PureWeen PureWeen merged commit 5b6db39 into net9.0 Jun 21, 2024
49 checks passed
@PureWeen PureWeen deleted the dev/pjc/net9-maestro-vers branch June 21, 2024 17:09
@github-actions github-actions bot locked and limited conversation to collaborators Jul 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-infrastructure CI, Maestro / Coherency, upstream dependencies/versions fixed-in-9.0.0-preview.6.24327.7
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants