[MDLSITE-2662] First public runs of prechecker against various criteria - Moodle Tracker

XML

Word

Printable

I'm going to perform a public (sending results to Tracker) run of all the issues awaiting integration right now (16 issues). Link: https://tracker.moodle.org/issues/?jql=text%20~%20%22text%20~MDLSITE-2662%22

I've sent a bulk comment to all them to let developers know, pointing to this issue for any comment/observation.

That is, feel free to comment anything. TIA!

blocks

MDLSITE-3267 New features to be added to the pre-checker

has a non-specific relationship to

MDLSITE-2287 Tracker integration (automated CI)

1.	When a run ends with error, no feedback is sent to Tracker	Closed	Eloy Lafuente (stronk7)
2.	Ignore JS/CSS files	Closed	Eloy Lafuente (stronk7)
3.	Subsystems are not handled ok by moodlecheck	Closed	Eloy Lafuente (stronk7)
4.	Remove the "ci" label if the issue is sent back to development/reopened	Closed	Eloy Lafuente (stronk7)
5.	Automate the "developer requested" prechecks...	Closed	Eloy Lafuente (stronk7)
6.	Automate the "awaiting peer-review" prechecks...	Closed	Eloy Lafuente (stronk7)
7.	Automate the "awaiting integration" prechecks...	Closed	Eloy Lafuente (stronk7)
8.	Reword a bit the messages from CiBoT	Resolved	Dan Poltawski
9.	Running the bulk checker leads to failed logins blocking the cibot account	Closed	Eloy Lafuente (stronk7)
10.	Move the constant 15d and 60d limits to params	Closed	Eloy Lafuente (stronk7)
11.	block_comments detected as an incorrect @package name	Closed	Eloy Lafuente (stronk7)
12.	Make all criterias to aways clean the cime label	Closed	Eloy Lafuente (stronk7)
13.	Add check for empty testing instructions	Resolved	Dan Poltawski

Participants:: Dan Poltawski, Eloy Lafuente (stronk7), Gareth J Barnard, Michael Aherne, Tim Hunt