Cold numbers:
17 issues have been successfully integrated with 0 rejected and 14 delayed. That's 100% success, second week in a row... uhm... that deserves a verification!
Notes:
- Last week, Code checker 3.0.0beta was released in the Plugins directory. It comes with the latest CodeSniffer release (3.5.8), our "moodle" ruleset and Sniffs converted to new 3.x ones, plus all the tests and utilities working apparently ok.
- Anybody wanting to try it, pick it from the link above or switch to the "phpcs3" branch via git.
- Since its release, it's being used by CiBoT and the Tracker reports, working without problems. If you find any glitch / bug, please keep us informed using GH issues.
- Soon, the 3.0.0 final version will be released (in the master branch) and we'll be spreading it over tools (CiBoT, moodle-plugin-ci) ASAP.
- As you may know, recently Travis changed their plans / pricing structure and the change has become in effect already. Basically it means that all the previous "Free" (Open Source) plans now get a number of credits and, once the credits are spent (they are basically processing time) you must ask them for more credits or start paying. Some points:
- First of all, I want to say "Big thanks! to Travis for all the resources that they have been giving to us for free over all these years, incredible!
- But, also, I think that we must find reliable alternatives (plural) to Travis, because it affects every-single Moodle repo we work with, and to everybody, Moodle HQ or no, core or plugin. And we shouldn't be subject to "surprises" like this (less than one month ago we were moving all the stuff from travis-ci.org to travis-ci.com without knowing that this was going to be announced and applied so quickly).
- In order to keep things working and to provide some good replacements for current travis-dependent stuff, some initiatives are already ongoing:
- Moodle HQ (and all their repos) are already using a paid Travis plan. That way all the pushes and pull requests to all our repos will continue being covered by current Travis CI checks.
- We are reducing the number of tests (saving minutes, aka credits) run by default in core. You can find some more information and details @ MDL-70265.
- Also for core, we have an initial version using GitHub Actions, and it's working acceptably well. That integration is specially interesting because it's free for public repos and integrates automatically for all the developers having their clones @ github. See MDL-70276 for more info (and an example of the new badges that soon we'll see in all issues). Of course it doesn't cover people using other git facilities, we are happy to add support for more, just share your ones in the issue.
- Something similar / parallel is happening with all the non-core repositories, we'll be gradually adding support for GH Actions to all them (codechecker, moodlecheck, local_ci, moodle-docker...)
- Special mention to moodle-plugin-ci, there you will find a number of issues related with the change (see #47, #48 and some other issues). The basic idea is to make/keep moodle-plugin-ci being CI agnostic so it can be used by a variété of systems, say travis, github actions, your local computer... or system X. That doesn't deny specific developments that can be done for better integration, but without putting on risk the functionality as a standalone product.
- Ideally, all the initiatives above, mainly focussed on GitHub Actions (that is a really cool CI approach) won't be the last and we'll be able to provide other, alternative, CI integrations, both for core and plugins.
- Finally, we don't have any immediate plan to remove any current Travis integration, so it should continue working exactly the same for everybody already into a paid plan (or planning to move to it). Simply, it has become "one more CI tool", from its previous "the main CI tool" role (for Moodle). Just that.
Hot topics:
- If all the above doesn't sound hot for you, I can respect it, but please, look to the list of issues yourself!
One at a time:
This (non-regular) section in the integration posts aims to get various policy issues communicated and, with your collaboration, decided and applied in an organised way.
- MDLSITE-2804 : This is due and decided, but haven't had time to process it yet, will try this week.
- MDL-69308: Moodle 3.11 requirements is the next one to be proposed for voting, if you've any suggestion or comment, now it's the time for them!
Warm thanks:
- To the Holidays, cannot wait for next ones.
After all, the best part of a holiday is perhaps
not so much to be resting yourself, as to see
all the other fellows busy working.
-- Kenneth Grahame