Test suites need to be faster as well. Once we work out ways to increase test isolation (for instance T90964) we should also work towards making them execute in parallel.

In T91669#1092979, @dduvall wrote:

Test suites need to be faster as well. Once we work out ways to increase test isolation (for instance T90964) we should also work towards making them execute in parallel.

The jobs that run on-commit (as opposed to from cron) should not in any way connect to beta labs, staging or other wikis outside the jenkins slave.

In T91669#1096332, @Krinkle wrote:

In T91669#1092979, @dduvall wrote:

Test suites need to be faster as well. Once we work out ways to increase test isolation (for instance T90964) we should also work towards making them execute in parallel.

The jobs that run on-commit (as opposed to from cron) should not in any way connect to beta labs, staging or other wikis outside the jenkins slave.

I should have been more clear: Whatever method/environment we use to isolate tests needs to support concurrency within a single browser test suite. I'm not sure that a one-mediawiki-installation-to-one-test-process setup is going to accommodate enough concurrency. You're right, though. It can't be performed on a wiki that's shared beyond the workspace and, since it's an isolated environment, users and other resources might as well be provisioned in a setup/teardown fashion instead of relying on pre-provisioned resource pools.

@greg do we still need this task or is now replaced by release pipeline?