moodle-plugin-ci
moodle-plugin-ci copied to clipboard
Assist with running a Moodle plugin in Travis CI
Hello, This PR add the ability to use this plugin inside a full Moodle repository and test multiple plugins already present in the repository (provided as submodules for example). It...
We should be able to run a check_database_schema.php check to confirm that all new installs and upgrades are in sync. So the CI plugin should grab the earliest verion of...
Added a check script that just runs admin/cli/check_db_schema. Note that the Moodle database must be installed during testing using admin/cli/install_database.php
Thanks again for having merged the `--no-init` option in #66. We have been successfully able to leverage it to use build stages in our projects (https://travis-ci.org/learnweb/moodle-repository_owncloud/builds/334743893, https://travis-ci.org/learnweb/moodle-mod_collaborativefolders/builds/328301352) and it's very...
This is on par with the moodle core requirement that every commit reference an MDL tracker. 90% of moodle plugin repos will use github so referencing a github issue via...
I'm not sure what is going on, but I'm hitting this: ``` $ moodle-plugin-ci install 4/7 [================>-----------] 57% 9 secs [Install dependencies] [Symfony\Component\Process\Exception\ProcessFailedException] The command "composer install --no-interaction --prefer-dist" failed....
We should check that all classes are in a correct namespace, ie they are implementing a core thing, or they are "\local": https://docs.moodle.org/dev/Coding_style#Rules_for_level2 https://docs.moodle.org/dev/Automatic_class_loading#Namespaces
I think there's a use case to be able to specify Behat tags -- for example, you might have a custom tag that you use to exclude tests that should...
travis support docker, so why not use docker with moodle-plugin-ci behat tests here my configuration (it's use chrome browser image) ```yaml sudo: required notifications: on_success: never #change #never # default:...
It seems like a Java problem (surprise surprise) Workaround: add `sudo: required` to .travis.yml