We have been setting up extensions to run against a daily catalyst environment, but we should also set core tests to run daily as a baseline.
Once in place, they can also be used in catalyst CI pipelines to ensure that any changes to not break the catalyst daily jobs.
AC:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| In Progress | vaughnwalters | T424411 [EPIC] Run selenium daily tests against a catalyst env (extensions with existing daily betacluster runs) | |||
| Resolved | vaughnwalters | T429629 Run core tests daily against a catalyst env | |||
| Resolved | vaughnwalters | T429707 Don't blank the main page on creation of single wiki environments | |||
| Resolved | vaughnwalters | T429829 Run tests for core first on catalyst daily |
Change #1304835 had a related patch set uploaded (by Vaughn Walters; author: Vaughn Walters):
[integration/config@master] jjb: [catalyst-daily-core] Add core job
Created T429707 to make sure that catalyst single wiki envs use the default setup. Merging this in after that patch lands.
Change #1304835 merged by jenkins-bot:
[integration/config@master] jjb: [catalyst-daily-core] Add core job
Change #1305214 had a related patch set uploaded (by Vaughn Walters; author: Vaughn Walters):
[integration/config@master] jjb: [catalyst-daily] Export deploy.env so selenium-test sees MW_SERVER
Change #1305214 merged by jenkins-bot:
[integration/config@master] jjb: [catalyst-daily-core] export Catalyst env