-
Notifications
You must be signed in to change notification settings - Fork 861
Fix signing for aspire-managed bundle payload #15990
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
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -52,9 +52,28 @@ steps: | |||||||||
| /p:BundleVersion=ci-bundlepayload | ||||||||||
| /p:SkipNativeBuild=true | ||||||||||
| /p:ContinuousIntegrationBuild=true | ||||||||||
| $(_SignArgs) | ||||||||||
| $(_OfficialBuildIdArgs) | ||||||||||
| /bl:${{ parameters.repoLogPath }}/BundlePayload-${{ targetRid }}.binlog | ||||||||||
| displayName: 🟣Build bundle payload (${{ targetRid }}) | ||||||||||
|
|
||||||||||
| - pwsh: | | ||||||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why are we trying to verify the signed status of the |
||||||||||
| $managedPath = Join-Path '${{ parameters.repoArtifactsPath }}/bin/Aspire.Managed/${{ parameters.buildConfig }}/net10.0/${{ targetRid }}/publish' 'aspire-managed.exe' | ||||||||||
| if (-not (Test-Path $managedPath)) { | ||||||||||
| Write-Host "##[error]aspire-managed.exe not found at $managedPath" | ||||||||||
| exit 1 | ||||||||||
| } | ||||||||||
|
|
||||||||||
| $signature = Get-AuthenticodeSignature $managedPath | ||||||||||
| if ($signature.Status -eq [System.Management.Automation.SignatureStatus]::NotSigned) { | ||||||||||
| Write-Host "##[error]aspire-managed.exe is not signed: $managedPath" | ||||||||||
|
||||||||||
| if ($signature.Status -eq [System.Management.Automation.SignatureStatus]::NotSigned) { | |
| Write-Host "##[error]aspire-managed.exe is not signed: $managedPath" | |
| if ($signature.Status -ne [System.Management.Automation.SignatureStatus]::Valid) { | |
| Write-Host "##[error]aspire-managed.exe has an invalid signature status '$($signature.Status)': $managedPath" |
Outdated
Copilot
AI
Apr 9, 2026
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.
The signature verification step is likely to run on PR builds where signing is disabled (e.g., _Sign is false and _SignArgs is empty). In that case aspire-managed.exe will legitimately be unsigned and this step will fail the pipeline. Update the condition to also require that signing is actually enabled (for example by checking variables['_Sign'] or that _SignArgs is non-empty).
| condition: and(succeeded(), eq(variables['Agent.OS'], 'Windows_NT'), in(variables['_SignType'], 'real', 'test'), startsWith('${{ targetRid }}', 'win-')) | |
| condition: and(succeeded(), eq(variables['Agent.OS'], 'Windows_NT'), eq(variables['_Sign'], 'true'), in(variables['_SignType'], 'real', 'test'), startsWith('${{ targetRid }}', 'win-')) |
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.
@radical @joperezr - do the sign args do anything here? I wouldn't think signing would happen during
dotnet publishof these projects, but instead at a later step that signs things in the output directory.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.
It usually happens as a post build step as you say, but here it might be a bit different and tricky given we are zipping the contents and bundling them into aspire exe. I'm looking at details here to see how we can orchestrate this so it works, and also seeing if the current implementation works or not.