Hi,
in an attempt to make testing Vim a bit easier, I created a Github repository
[1] that uses Travis CI to compile Vim and run the tests.
This is a proof-of-concept right now and only builds for Linux (Ubuntu 12.04
with GCC 4.6.3 and Clang 3.4) with different feature sets (tiny, ...). See [2]
for the build script.
It should be fairly easy to extend it to build on OS X (currently in Beta on
Travis CI) and Windows (using AppVeyor), or e.g. to use different compiler
versions.
It currently does two things:
1. Building of latest Vim version
Pulls latest Vim from its Mercurial sources, compiles it and runs the tests.
See [3] for a build of current Vim (7.4.582), which I think already uncovered a
problem: Running the tests fails with tiny and small features ("test16 NO
OUTPUT"), but works with bigger feature sets.
These builds are currently triggered manually, but could easily be turned into
nightly builds by using a cron job.
2. Testing of patches
A pull request containing patches can be created on Github (Example: [4]),
triggering a build that applies these patches before Vim is compiled and tests
are run. This could be used by contributors to test Vim patches.
As I said in the beginning, this is only an experiment for now, so please let
me know whether you think this could be useful.
Cheers,
Florian
[1] https://github.com/fwalch/vim-ci
[2] https://github.com/fwalch/vim-ci/blob/master/.travis.yml
[3] https://travis-ci.org/fwalch/vim-ci/builds/47524660
[4] https://github.com/fwalch/vim-ci/pull/1
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
