-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Add task for packaging release #6
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
Conversation
2b35d4f
to
5478f3a
Compare
b9894d3
to
69133cb
Compare
Optimally we'd fix the |
This is so it can be used as part of the build/release script.
561e786
to
85c192e
Compare
runner.cwd = releasePath; | ||
await os.platform() === "linux" | ||
? runner.execute("tar", ["-cvzf", `${archiveName}.tar.gz`, `${archiveName}`]) | ||
: runner.execute("zip", ["-r", `${archiveName}.zip`, `${archiveName}`]); |
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.
For our use case, is tar preferable to zip? And if so, is there any way for us to set a conditional based on whether or not said commands are installed rather than OS platform? Or is it inconsequential and/or not worth the time?
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.
The goal is to provide tarballs for Linux builds and zips for Mac & Windows builds. This runs in the CI and is what will be available for download on the releases page.
* Add task for packaging release * Modify package task to package a single binary This is so it can be used as part of the build/release script. * Package release as part of Travis deploy * Set platform env var * Add arch env var * Make version available to the code * Use tar for Linux and zip for Mac & Windows
No description provided.