-
Notifications
You must be signed in to change notification settings - Fork 356
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
Updating build to use Azure DevOps #2944
Conversation
$ctx = New-AzureStorageContext $env:FILES_ACCOUNT_NAME $env:FILES_ACCOUNT_KEY | ||
Set-AzureStorageBlobContent "$directoryPath/../../../buildoutput/tosign.zip" "webjobs" -Blob "$env:APPVEYOR_BUILD_VERSION.zip" -Context $ctx | ||
Write-Host "Uploading signing job to storage." | ||
# This will fail if the artifacts already exist. |
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.
great addition! love finding comments like this when I investigate issues.
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 to me -- just one question about signing...
testRunTitle: 'XUnit Tests' | ||
condition: always() | ||
|
||
- pwsh: .\tools\PollSigningResults.ps1 -buildVersion "$(buildVersion)" -isPr $$(isPr) -artifactDirectory "$(buildOutputDirectory)" -forceArtifacts $${{ parameters.force_artifacts }} -skipAssemblySigning $${{ parameters.skip_assembly_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.
Is the plan to move to the ADO signing task once this is in and stabilized?
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 question; I would assume so. The goal of this work is a lift-and-shift to ADO with minimal adjustments to get things working in the new environment. We've got a high-level tracking item for enhancements identified during but outside the scope of the migration epic here: Azure/Azure-Functions#2272
@fabiocav to confirm, but I'll create a work item for this.
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.
Work item: #2948
d274e80
to
60370da
Compare
Issue describing the changes in this PR
addresses Azure/azure-functions-host#8757
Pull request checklist
release_notes.md
Additional information
A couple changes to note: