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

Updating build to use Azure DevOps #2944

Merged
merged 1 commit into from
Jan 18, 2023
Merged

Updating build to use Azure DevOps #2944

merged 1 commit into from
Jan 18, 2023

Conversation

kashimiz
Copy link
Contributor

@kashimiz kashimiz commented Jan 4, 2023

Issue describing the changes in this PR

addresses Azure/azure-functions-host#8757

Pull request checklist

  • My changes do not require documentation changes
    • Otherwise: Documentation issue linked to PR
  • My changes should not be added to the release notes for the next release
    • Otherwise: I've added my notes to release_notes.md
  • My changes do not need to be backported to a previous version
    • Otherwise: Backport tracked by issue/PR #issue_or_pr
  • My changes do not require diagnostic events changes
    • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
  • I have added all required tests (Unit tests, E2E tests)

Additional information

A couple changes to note:

  • Because this branch removes the appveyor.yaml file, the AppVeyor build will not complete as part of the checks. The build that matters is the one on ADO.
  • Some tests that passed locally and on AppVeyor failed on the ADO build agent. Some were flaky and impeded migration by failing runs. They were disabled in order to proceed, but issues to investigate and fix them have been created. See tracking issue Re-enable Tests: SingletonListener and SingletonTrigger #2945

azure-pipelines.yml Show resolved Hide resolved
$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.
Copy link
Member

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.

Copy link
Member

@brettsam brettsam left a 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 }}
Copy link
Member

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?

Copy link
Contributor Author

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Work item: #2948

@kashimiz kashimiz force-pushed the kashimiz/adomigration branch from d274e80 to 60370da Compare January 18, 2023 18:02
@kashimiz kashimiz merged commit 01a8cfd into dev Jan 18, 2023
@kashimiz kashimiz deleted the kashimiz/adomigration branch January 18, 2023 19:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants