-
Notifications
You must be signed in to change notification settings - Fork 1
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
Added GitHub Actions Workflows CI_CD #32 #38
Conversation
.github/workflows/build.yaml
Outdated
- name: Upload artifact | ||
uses: actions/upload-artifact@v2 | ||
with: | ||
name: program-zip |
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 the program right now is called grout-wm
, maybe the zip-file should be called grout-wm.zip
? Also, would it be possible to get the version number from Cargo.toml? So the file would be grout-wm-version.zip
?
.github/workflows/build.yaml
Outdated
|
||
jobs: | ||
test: | ||
runs-on: ubuntu-latest |
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.
Linux? Since its a program for Microsoft Windows, does a build on linux produce a windows exe?
Did some necessary changes. Can you review it now if it's fine now. |
@PratikKumar125 Thank you. |
Whenever a new PR will be created or updated the workflow will run "cargo clippy" and "cargo test".
And depending upon it's results, after a successful merging to master branch, it will run the "cargo build" and will save the artifacts.