This task is to explore what we can do to make Zuul give feedback earlier to developers once one job has failed. There are a number of ways this could be addressed:
- (Basic) Once one job fails, abort the others and submit the comment to Gerrit.
- (Ideal) Configure in Zuul which jobs are fast/mandatory and which are allowed to be aborted if others have already found failures. For example, if a PHPUnit or QUnit test is failing, it might be due to a syntax error. When that is the case, it is likely that the PHPCS (mediawiki-…-composer-test) and ESLint (mwgate-node) jobs have information that better explains this error. In general, it is likely that these will finish first anyway because they are much quicker. But it would be ideal to enforce this so that we are never in a situation where a developer is unable to get PHPCS or ESLint feedback.
- (Amazing?)
- Somehow edit the comment after initial submission so that we can keep adding details as we go.
- Use some kind of "Commit Status API" (like GitHub). Gerrit upstream is working on this and this would integrate the results of individual jobs much deeper in the Gerrit interface without any need for "bot comments", and without having to expose the details of the "pipeline" to Gerrit users.
- …