-
-
Notifications
You must be signed in to change notification settings - Fork 767
Retire AppVeyor, ensure GitHub actions has feature parity #17878
Copy link
Copy link
Closed
Labels
audience/nvda-devPR or issue is relevant to NVDA / Add-on developersPR or issue is relevant to NVDA / Add-on developersp5https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityrelease/blockingthis issue blocks the milestone releasethis issue blocks the milestone releaserelease/blocking-betatriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Milestone
Metadata
Metadata
Assignees
Labels
audience/nvda-devPR or issue is relevant to NVDA / Add-on developersPR or issue is relevant to NVDA / Add-on developersp5https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityrelease/blockingthis issue blocks the milestone releasethis issue blocks the milestone releaserelease/blocking-betatriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Related issues, PRs or discussions
Follow up to #17728 and #10516
What is the current state of the codebase?
After #17728 is merged, NVDA is now being built with GitHub actions in parallel to AppVeyor.
It is missing key parts of AppVeyor, many required to create a release build of NVDA:
Why are changes required?
We want parity between GitHub actions and AppVeyor before migrating over permanently
What technical changes are required?
Are the proposed technical changes API breaking?
No
Are there potential risks or issues with the proposed implementation?
No