wjunkin
commented
5 years ago Thanks, Dan, I am running Github on my own laptop (running XAMPP) and I then transfer the code to the https://github.com/wjunkin/ Github site. I tried to put travis-ci into the system but had some problems. I always check my code against "code checker" and "Moodle PHPdoc check." Obviously it would save me time if I was able to use travis-ci. I plan to see what I can do about this for future development, but for now I am skipping this.
After fixing issue #1 you might consider adding support for travis ci to your plugin.
Some of the tests run by the Moodle.org plugins db can be run via travis-ci on each commit in your github repo. Enabling Travis integration helps you to make sure future changes to your plugin will continue to follow the guidelines.
More information on this is here: https://moodle.org/mod/forum/discuss.php?d=323384
but the short version: grab this file: https://github.com/moodlerooms/moodle-plugin-ci/blob/master/.travis.dist.yml rename it as .travis.yml and put in the root of your github directory. Go to: https://travis-ci.org/profile/wjunkin Flick the switch for this repo.
then on every commit you make to github it will fire off a request to travis to run the tests in .travis.yml and will give you traffic lights beside each commit and generate a report.
something else you might want to change: in .travis.yml the default file has this line:
env: global:
MOODLE_BRANCH=MOODLE_32_STABLE you might want to add other branches to that list - so you might want to change it something like:
env: global:
MOODLE_BRANCH=MOODLE_33_STABLE MOODLE_BRANCH=MOODLE_34_STABLE MOODLE_BRANCH=MOODLE_35_STABLE