Conversation
Treated warnings as errors. Added current dir to include path ($PWD and %CD%). Set low verbosity.
|
While you at it, can you remove 1.8 from the build matrix and update it to build against the newest SM development version (1.11) and allow it to fail. |
|
Updated SM versions and i'm added matrix for AppVeyor. (It's so fun. I did this changes in last night and in three hours before when i'm start RP, Alliedmodders have decided bump version) |
Done and tested. Results with test error: (Travis) (appveyor) |
|
Why we need both (travis and appveyor)? |
|
We can work with github actions and "runs-on" for compiling under linux and windows. |
|
We could always move to Github's actions down the road; as of right now Github's action is still in a premature state, at least from my experience trying to use it in a Golang project. |
|
I already setuped GitHub Actions for own periodically building plugins. You can try "rewrite" my config. |
|
There are a few issues that I'm waiting on to be resolved with actions, so we can potentially have multi-workflow builds and jobs for this repo and the doc repo. Upload Artifact
Download Artifact
Github Universe 2019 is about a month away; I suspect by then it'll be out of beta. |
|
@rumblefrog or disable artifact uploads at the beginning. and just compiling the plugins to get the logs. |
5 participants
Motivation and Context
Treated warnings as errors (flag -E).Any warnings is potentially maybe issue. It is better to avoid warnings.
Added current dir to include path ($PWD and %CD%)(flag -I<name>).For prevent failed build. See: #625
Set low verbosity (flag -v<num>).Just less output info like sourcemod compiler version and
done.message.How Has This Been Tested?
Tested:
1.x branch here: (Travis) (appveyor)
For PR here: (Travis) (appveyor)
Types of changes
Checklist: