Change Details

== Background Changes in MediaWiki core have potential to break the ReadingLists extension. (see T403560) == Goal We need a way to either prevent this from happening (e.g. gate-and-submit) or be notified when the ReadingLIsts tests on the master branch are broken. === Developer notes Options: 1. Add ReadingLists extension to the gate-and-submit job, but this has many downsides, especially that it involves running the tests for patches on all extensions. 2. Define a more fine grained set of dependencies (e.g. Vector, Minerva and core) which should have ReadingLists tests run as a less onerous version of gate-and-submit. This is not possible at the moment. 3. Setup a daily job on jenkins to run ReadingLists tests. (e.g. as if a patch was submitted to the ReadingLists extension). If the tests are failing, then an email and slack notification(s) should be sent. Having a daily test job for ReadingLists is the most feasible to be alerted to any breakage in tests so that engineers can fix the issue. Further documentation: https://wikitech.wikimedia.org/wiki/PipelineLib/Guides/How_to_configure_CI_for_your_project == Acceptance criteria for done [] Clarify option [] Reach out to developer experience team? #developer-experience / releng [] Implement favorable option

== Background Changes in MediaWiki core have potential to break the ReadingLists extension. (see T403560) == Goal We need a way to either prevent this from happening (e.g. gate-and-submit) or be notified when the ReadingLIsts tests on the master branch are broken. === Developer notes Options: 1. Add ReadingLists extension to the gate-and-submit job, but this has many downsides, especially that it involves running the tests for patches on all extensions. 2. Define a more fine grained set of dependencies (e.g. Vector, Minerva and core) which should have ReadingLists tests run as a less onerous version of gate-and-submit. This is not possible at the moment. 3. Setup a daily job on jenkins to run ReadingLists tests. (e.g. as if a patch was submitted to the ReadingLists extension). If the tests are failing, then an email and slack notification(s) should be sent. Having a daily test job for ReadingLists is the most feasible to be alerted to any breakage in tests so that engineers can fix the issue. == Acceptance criteria for done [] Clarify option [] Reach out to developer experience team? #developer-experience / releng [] Implement favorable option

== Background Changes in MediaWiki core have potential to break the ReadingLists extension. (see T403560) == Goal We need a way to either prevent this from happening (e.g. gate-and-submit) or be notified when the ReadingLIsts tests on the master branch are broken. === Developer notes Options: 1. Add ReadingLists extension to the gate-and-submit job, but this has many downsides, especially that it involves running the tests for patches on all extensions. 2. Define a more fine grained set of dependencies (e.g. Vector, Minerva and core) which should have ReadingLists tests run as a less onerous version of gate-and-submit. This is not possible at the moment. 3. Setup a daily job on jenkins to run ReadingLists tests. (e.g. as if a patch was submitted to the ReadingLists extension). If the tests are failing, then an email and slack notification(s) should be sent. Having a daily test job for ReadingLists is the most feasible to be alerted to any breakage in tests so that engineers can fix the issue. Further documentation: https://wikitech.wikimedia.org/wiki/PipelineLib/Guides/How_to_configure_CI_for_your_project == Acceptance criteria for done [] Clarify option [] Reach out to developer experience team? #developer-experience / releng [] Implement favorable option