-
Notifications
You must be signed in to change notification settings - Fork 834
Updates to wheel deployment workflow #5386
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
Open
IAlibay
wants to merge
6
commits into
develop
Choose a base branch
from
deploy-testing
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+16
−10
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
aa9ca15
Add workflow dispatch trigger to deployments for testing
IAlibay 746ac31
Update deployment workflow, including new arm wheels
IAlibay 2346799
Need arch in name
IAlibay e2253a2
Apply suggestion from @IAlibay
IAlibay a99cfd7
may require capitalized AMD64
IAlibay c9e70fc
Update deploy.yaml
IAlibay File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
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.
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.
Do we really want to target builds for intel macs? Can't builds for those be dropped and if someone requires it they can always build themselves?
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.
My take is here is "why not" - there's not really a cost to having them. Is the concern mostly that we don't test it anymore?
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.
I'd still build them as long as it does not break our system. Not everyone can afford upgrading their laptop every 3 years (yes, M1 was ~2020...) and so providing our software on older architectures makes it more accessible.
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.
I mention mostly because Blender has dropped providing explicit binaries for Intel Mac's because of the development burden. As long as it's not breaking anything then I suppose why not, but I think if it starts causing issues we drop it.
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.
My suggestion is that we add intel osx back into the cron test matrix. I am a little bit wary that we've not run tests with it in a while, so have it solely in deployment seems risky.