Separate appveyor projects #12615
Merged
Separate appveyor projects #12615
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
See completed build of commit bea26e3c0d |
feerrenrut
approved these changes
Jul 7, 2021
There was a problem hiding this comment.
Looks good to me. I think @michaelDCurran should also review this.
michaelDCurran
approved these changes
Jul 9, 2021
If many PR/try builds are queued, it can take a long time to build a release. Building tagged releases is an involved process for an NV Access developer and as such, should be prioritised. This commit creates two separate new projects for tagged releases and other builds. This allows for priorities to be set in the online UI.
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Link to issue number:
None
Summary of the issue:
If many PR/try builds are queued, it can take a long time to build a release. Building tagged releases is an involved process for an NV Access developer and as such, should be prioritised.
Description of how this pull request fixes the issue:
Creates two separate new projects for tagged releases and other builds. This allows for priorities to be set in the online UI.
The merge strategy is to squash all the code changes after the move into one commit, and perform a merge commit.
Testing strategy:
Confirming the following diffs are expected
Known issues with pull request:
None
Change log entries:
None
Code Review Checklist: