Stop using AppVeyor as a CI
#19089
Replies: 3 comments 3 replies
|
Since AppVeyor doesn't run jobs in parallel, the last pull request in the queue can end up waiting for hours. Having each developer wait that long is very inefficient. I am also in favor of dropping AppVeyor. |
0 replies
|
Currently We can download compiled artifacts on it. Before stop using it, maybe we should support it on github first. |
1 reply
|
For example, we can stop the tests. |
|
I believe some code issues did only occur on Appveyor? Like some of the size_t int conversion issues. On the other hand, we probably notice those using the |
2 replies
|
BTW, test can be disabled with comment-out. diff --git a/appveyor.yml b/appveyor.yml
index 342db9c..ce4defa 100644
--- a/appveyor.yml
+++ b/appveyor.yml
@@ -39,8 +39,8 @@ build_script:
after_build:
- '"%APPVEYOR_BUILD_FOLDER%\appveyor.bat" package'
-test_script:
- - '"%APPVEYOR_BUILD_FOLDER%\appveyor.bat" test'
+#test_script:
+# - '"%APPVEYOR_BUILD_FOLDER%\appveyor.bat" test'
artifacts:
- path: gvim_*_x86.zip |
|
Could you please start a PR? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
What if we stopped using AppVeyor as a CI?
The bad thing about AppVeyor is that it limits parallel execution to one.
I'm aware that AppVeyor was previously the only CI available for Windows.
However, now that GitHub Actions also supports Windows runners,
doesn't that mean we no longer have to use AppVeyor?
If anyone knows why AppVeyor is necessary, please let me know.
All reactions