This repository was archived by the owner on Dec 5, 2024. It is now read-only.
Create unitypackage packages in CI #915
Merged
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
shana
force-pushed
the
automating-releases
branch
5 times, most recently
from
04536a0 to
af15813
Compare
shana
force-pushed
the
automating-releases
branch
from
af15813 to
c623b51
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Adding a typescript command line tool (in the packaging submodule) that takes the contents of the unity/PackageProject folder after the build and tests run and creates a unitypackage out of it, uploading it as an artifact. mdb symbol files are generated from the pdb files that VS creates using pdb2mdb.exe (in the lib folder).
The version of the build is now also on appveyor.yml so that deployments to GitHub Releases can create a release with the correct version. The packages and zip files are stamped with the version that's in SolutionInfo.cs + the appveyor build number.
Unfortunately, I don't know how to get the deployment to pick up the version that's set in the SolutionInfo file, so it picks up the version that's defined in the appveyor.yml file. We can always fix the version the release after the deployment, since it's a draft, so that shouldn't be too much of a problem.