Skip to content
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

Generate RuSTy Binaries on push #183

Closed
ghaith opened this issue Jul 1, 2021 · 0 comments · Fixed by #185
Closed

Generate RuSTy Binaries on push #183

ghaith opened this issue Jul 1, 2021 · 0 comments · Fixed by #185
Assignees
Labels
ci Build process
Projects

Comments

@ghaith
Copy link
Collaborator

ghaith commented Jul 1, 2021

Is your feature request related to a problem? Please describe.
We should try and publish binaries for windows and Linux ideally on every change on master, but if not possible then on every release.

Describe the solution you'd like
When a git push on master happens, the build artifacts will be available for download
See : https://github.com/actions/upload-artifact
The files we would provide are :

  • Linux standard binary (x86_64-unknown-linux-gnu)
  • Standalone linux binary (x86_64-unknown-linux-musl)
  • Windows standalone binary for 64bit windows

When building a release, these artifacts should be automatically uploaded to the release assets.

Additional context
This feature would provide quick access to our latest binary to use while testing without having to install a full rust and llvm toolchain. The required LLVM toolchain is hard to install on windows

@ghaith ghaith self-assigned this Jul 1, 2021
@ghaith ghaith added the ci Build process label Jul 1, 2021
@ghaith ghaith added this to To do in Next via automation Jul 1, 2021
@ghaith ghaith moved this from To do to In progress in Next Jul 1, 2021
Next automation moved this from In progress to Done Jul 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Build process
Projects
Status: Done
Next
Done
Development

Successfully merging a pull request may close this issue.

1 participant