Add yamato configurations for building and uploading artifact to Stevedore. #42
Conversation
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
brian-taylor-unity
force-pushed
the
yamato-create-stevedore-artifacts
branch
8 times, most recently
from
0ba9ee3 to
e0ff9f7
Compare
brian-taylor-unity
force-pushed
the
yamato-create-stevedore-artifacts
branch
3 times, most recently
from
0d51bf2 to
56e0717
Compare
…otnet-unity' to fit within character limit on stevedore.
brian-taylor-unity
force-pushed
the
yamato-create-stevedore-artifacts
branch
from
56e0717 to
41f1bd8
Compare
|
I'll need to change the Github PR checks after merging this to reflect the new names of yamato configs. |
UnityAlex
approved these changes
Feb 25, 2022
joshpeterson
approved these changes
Feb 25, 2022
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.
Added yamato configurations for uploading runtime artifacts to stevedore for Windows x86, Windows x64, OSX x64, and Linux x64.
I separated the build+test yamato configs into separate build and test configs, where the test and publish-to-stevedore configs are dependent on the build configs.
Build configs will generate artifacts for both the full directory structure and for just the runtime 7z we use for stevedore. I have the build configs generate the stevedore artifacts instead of the publish-to-stevedore configs because a developer might want to get a built .7z for local testing before actually publishing that build to stevedore.
Test configs will still trigger on any PR targeting trunk, but publish-to-stevedore configs are all manual. There is a top-level "Publish to Stevedore" config that will trigger all of the platforms' publish-to-stevedore configs.
Where we publish the artifacts to (
testing,unity-internal, orpublic) is set and can be changed in.yamato\Globals.metafile.