-
Notifications
You must be signed in to change notification settings - Fork 2
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
CI Tool : Github Action #3
Comments
Never used Travis before but I'm OK with it. |
Travis CI basically creates a Virtual Machine, according to our Travis File, it clones our repository, downloads all required tools such as compilers, and calls our makefile to run tests. If there is an error, it blocks the pull request in the GitHub. In the GitHub Pull Request Page, you see a window which shows all whether tests pass or not. |
@alifiratari @volkanunal For example; in the Travis-CI, It was cloning the repo automatically, but I was installing some tools which were required for tests like below;
Can we do that? The ideal CI approach should be we should be able to run the same tests in our local and the server(Pull Request). Herein we need to use the same command to run all tests in both local and remote. |
Added blank CI project --> pull request #9 It is posibble. add the commands to end of .github/workflows/blank.yml
|
@alifiratari That's awesome. Thanks. |
|
The requirements could be like below
1 - Easy to use
2 - Fully Github Integration (Needs to block the Pull Requests which do not pass all CI tests)
3 - Free
Jenkins is widely used for CI but it is awful so we can use Travis-CI here which is fully integrated with Github and free for Open-Source Projects and widely used by open source projects too.
The text was updated successfully, but these errors were encountered: