aboutsummaryrefslogtreecommitdiff
path: root/appveyor.yml (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Use luarocks-3 branch on AppveyorHisham2016-10-191-1/+1
|
* Merge branch 'master' into luarocks-3Hisham2016-10-141-12/+37
|\
| * Put MinGW in PATH for hererocks tooHisham2016-08-221-1/+2
| |
| * Build Lua using the same compiler as the one we're testingHisham2016-08-221-10/+10
| |
| * Add support for testing using MinGWHisham2016-08-221-1/+17
| |
| * Update of YAML files, changed coveralls for codecovroboo2016-08-211-13/+21
| |
* | Core modules reorganization.Hisham2016-06-301-2/+2
|/ | | | | | | | | | | | | | | | | | | | | | | | Isolate all modules used by luarocks.loader in a luarocks.core.* namespace. Core modules can only require other core modules, and they only use require() at the top-level chunk. In other words, after luarocks.loader is setup, package.path can be altered at will and it should not affect the ability of luarocks.loader to run, and the luarocks.loader modules should not interfere with modules loaded later. This was motivated by @robooo's GSoC work on porting the LuaRocks test suite to Lua using Busted. Busted itself runs using luarocks.loader, and we need to ensure that the modules loaded by the tests do not conflict with the ones used by luarocks.loader. A circular dependency between luarocks.manif and luarocks.search was removed by creating a separate luarocks.manif.writer module. Also, luarocks-admin commands were moved to a luarocks.admin.* namespace.
* ci: updates appveyor config to use VS2015.Peter Jas2015-08-181-5/+2
|
* Update appveyor test matrix to use Lua 5.3.1Ignacio Burgueño2015-06-251-1/+1
|
* Use LuaJIT 2.0.4 on AppVeyor's test matrixIgnacio Burgueño2015-06-081-1/+1
|
* Improved the CI scriptsIgnacio Burgueño2015-03-271-34/+17
| | | | | | | Ported back part of the work made [here](https://github.com/ignacio/lua-appveyor-example) by @moteus and me. I still need to write a test runner of sorts.
* Adds integration with AppVeyorIgnacio Burgueño2015-03-201-0/+50
Adds a simple integration with AppVeyor, defines a matrix to test with Lua 5.1, 5.2 and 5.3, and runs a couple of tests. This last part (the actual running of the tests), should be moved to a different file. Some kind of test runner should be built. But this is a start.