Closed danielneis closed 8 years ago
I've played around with this (we use gitlab for private projects). The first major road block would be the ability to configure the database host, as gitlab jobs often run with linked containers.
The tool supports configuring db connection:
Output from moodle-plugin-ci help install
Usage:
install [options]
Options:
--moodle=MOODLE Clone Moodle to this directory [default: "moodle"]
--data=DATA Directory create for Moodle data files [default: "moodledata"]
--branch=BRANCH Moodle git branch to clone, EG: MOODLE_29_STABLE
--plugin=PLUGIN Path to Moodle plugin
--db-type=DB-TYPE Database type, mysqli or pgsql
--db-user=DB-USER Database user
--db-pass=DB-PASS Database pass [default: ""]
--db-name=DB-NAME Database name [default: "moodle"]
--db-host=DB-HOST Database host [default: "localhost"]
--not-paths=NOT-PATHS CSV of file paths to exclude
--not-names=NOT-NAMES CSV of file names to exclude
-h, --help Display this help message
-q, --quiet Do not output any message
-V, --version Display this application version
--ansi Force ANSI output
--no-ansi Disable ANSI output
-n, --no-interaction Do not ask any interactive question
-v|vv|vvv, --verbose Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug
Help:
Install everything required for CI testing
fixed by #15
GitLab CI uses a .gitlab-ci.yml file similar to the .travis.yml file to run continuous integration jobs. As GitLab is free and open-source, it would be good to support it too even most developers do not use it yet for most public work, GitLab may be installed inside your organization to host your private projects. Here the documentation about the .gitlab-ci.yml file: http://doc.gitlab.com/ce/ci/yaml/README.html