-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add macOS and Windows builds and update versions #11
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
528f5ef
Upgrade Unity version to v2021
davidmfinol 4f93c26
Update workflow
davidmfinol 2d9d5cc
Update workflows
davidmfinol 16140a9
Add il2cpp and windows and mac workflows
davidmfinol 534ce26
Move windows
davidmfinol b012c98
Parallelize mac with linux
davidmfinol 45230a3
Add Unity secrets
davidmfinol b16a5de
Update to v2021.3.2f1
davidmfinol 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 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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
%YAML 1.1 | ||
%TAG !u! tag:unity3d.com,2011: | ||
--- !u!387306366 &1 | ||
MemorySettings: | ||
m_ObjectHideFlags: 0 | ||
m_EditorMemorySettings: | ||
m_MainAllocatorBlockSize: -1 | ||
m_ThreadAllocatorBlockSize: -1 | ||
m_MainGfxBlockSize: -1 | ||
m_ThreadGfxBlockSize: -1 | ||
m_CacheBlockSize: -1 | ||
m_TypetreeBlockSize: -1 | ||
m_ProfilerBlockSize: -1 | ||
m_ProfilerEditorBlockSize: -1 | ||
m_BucketAllocatorGranularity: -1 | ||
m_BucketAllocatorBucketsCount: -1 | ||
m_BucketAllocatorBlockSize: -1 | ||
m_BucketAllocatorBlockCount: -1 | ||
m_ProfilerBucketAllocatorGranularity: -1 | ||
m_ProfilerBucketAllocatorBucketsCount: -1 | ||
m_ProfilerBucketAllocatorBlockSize: -1 | ||
m_ProfilerBucketAllocatorBlockCount: -1 | ||
m_TempAllocatorSizeMain: -1 | ||
m_JobTempAllocatorBlockSize: -1 | ||
m_BackgroundJobTempAllocatorBlockSize: -1 | ||
m_JobTempAllocatorReducedBlockSize: -1 | ||
m_TempAllocatorSizeGIBakingWorker: -1 | ||
m_TempAllocatorSizeNavMeshWorker: -1 | ||
m_TempAllocatorSizeAudioWorker: -1 | ||
m_TempAllocatorSizeCloudWorker: -1 | ||
m_TempAllocatorSizeGfx: -1 | ||
m_TempAllocatorSizeJobWorker: -1 | ||
m_TempAllocatorSizeBackgroundWorker: -1 | ||
m_TempAllocatorSizePreloadManager: -1 | ||
m_PlatformMemorySettings: {} |
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.
If you have
pull_request
andpush
, then commits to PRs will trigger tests twice.After merging something to
main
the tests should ideally run again, and in case a commit needs to be made to main directly it should also run the workflow. This is whypush
only included upstream branch names.Not sure if you covered these cases in some other way somehow?
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.
Since this uses a personal license instead of a professional license, it should be fine if there are two instances of the workflow running at the same time, right? The
pull_request
workflow should use our credentials from our upstream repo, while thepush
workflow would use the user's credentials from their fork. Is there a potential problem with having the two workflow runs?I've personally found it very useful to have the tests run on every push. It's been especially useful to confirm each commit in a feature branch.
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 see. I don't know but a pull request from both local and a fork should just work as expected with the
pull_request
trigger. But I could be wrong?Yes actually we're hitting organisation-wide limits a lot with regards to runners, and the amount provided has become tighter as well a few months ago. When docker repo is building it's already stalling a lot for each commit, other repos don't currently have this by themselves, but they would block docker repo workflows.
However as the effect is probably quite minor I have no problem with moving forward with your changes if it solves a problem. Still trying to understand why push would be needed on all branches if a push to a PR already triggers on
pull_request
(asPR updated
) afaik.