Composer: Difference between revisions
From MoodleDocs
(Update version of moodle) |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 7: | Line 7: | ||
{ | { | ||
"type": "vcs", | "type": "vcs", | ||
"url": "https:// | "url": "https://github.com/moodle/moodle.git" | ||
} | } | ||
], | ], | ||
"require": { | "require": { | ||
"moodle/moodle": "v3. | "moodle/moodle": "v3.9.0" | ||
} | } | ||
} | } | ||
| Line 17: | Line 17: | ||
And then execute | And then execute | ||
<code>php composer.phar install</code> | <code>php composer.phar install</code> | ||
= How to prepare and submit composer changes = | |||
There are a number of situations where we need to update the bundled [https://github.com/moodle/moodle/blob/master/composer.json composer.json]] in core. When we upgrade, for a given branch, [https://tracker.moodle.org/browse/MDL-61678 the phpunit] or [https://tracker.moodle.org/browse/MDL-64409 the behat-extension] versions... we also have to update the [https://github.com/moodle/moodle/blob/master/composer.lock composer.lock] file, in order to guarantee that all the tests will run in a stable, verified environment. | |||
As far as there are a number of variables affecting how that lock file will be generated, here there are some standard steps to follow, in order to guarantee that any change to composer will be always applied in the same, standard and verified way. | |||
# Pre-requisite: Always use the '''lower PHP version supported''' in the branch the changes are happening. So, if a given branch (MOODLE_37_STABLE) works with PHP 7.1, 7.2 and 7.3...all the following steps will be executed using PHP 7.1 (the lower version supported). | |||
# Perform the required changes to the composer.json file. Normally. | |||
# Remove the composer.lock file that is going to be regenerated. <code>rm composer.lock</code> | |||
# Remove completely the vendor directory. <code>rm -fr vendor</code> | |||
# Clean all composer caches. <code>php composer.phar clearcache</code> | |||
# Run <code>php composer.phar update</code>, a new composer.lock will be regenerated. | |||
# Check that the composer.lock file, together with other changes, does include the changes you've performed in the composer.json file. | |||
# Ideally, run both phpunit and behat tests and verify that there isn't any problem, using all the supported PHP versions. | |||
# Done, you can send the changes for review, integration and, if everything goes ok, will be applied upstream without problem. | |||
Ciao :-) | |||
Revision as of 02:44, 5 July 2020
Use composer to download moodle code
Composer.json now includes meta information and hence composer can be used to download the moodle code base.
You can do it by creating composer.json file with following information
{
"repositories": [
{
"type": "vcs",
"url": "https://github.com/moodle/moodle.git"
}
],
"require": {
"moodle/moodle": "v3.9.0"
}
}
And then execute
php composer.phar install
How to prepare and submit composer changes
There are a number of situations where we need to update the bundled composer.json] in core. When we upgrade, for a given branch, the phpunit or the behat-extension versions... we also have to update the composer.lock file, in order to guarantee that all the tests will run in a stable, verified environment.
As far as there are a number of variables affecting how that lock file will be generated, here there are some standard steps to follow, in order to guarantee that any change to composer will be always applied in the same, standard and verified way.
- Pre-requisite: Always use the lower PHP version supported in the branch the changes are happening. So, if a given branch (MOODLE_37_STABLE) works with PHP 7.1, 7.2 and 7.3...all the following steps will be executed using PHP 7.1 (the lower version supported).
- Perform the required changes to the composer.json file. Normally.
- Remove the composer.lock file that is going to be regenerated.
rm composer.lock - Remove completely the vendor directory.
rm -fr vendor - Clean all composer caches.
php composer.phar clearcache - Run
php composer.phar update, a new composer.lock will be regenerated. - Check that the composer.lock file, together with other changes, does include the changes you've performed in the composer.json file.
- Ideally, run both phpunit and behat tests and verify that there isn't any problem, using all the supported PHP versions.
- Done, you can send the changes for review, integration and, if everything goes ok, will be applied upstream without problem.
Ciao :-)
