The catalyst-daily-* jobs can fail when the teardown publisher's castor-save trigger fails to start its downstream job on the castor node, even though Selenium passed and the environment was torn down cleanly. castor-save is a no-op on the daily pipeline anyway, so drop it and use docker-cleanup instead.
see https://integration.wikimedia.org/ci/view/selenium-daily/job/catalyst-daily-Newsletter/7/console or P94808 for an example of this failure
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| jjb: [catalyst-daily-*] Replace castor-save to stop transient build failures | Vaughn Walters | integration/config | master | +1 -1 |
| 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 | T432047 Drop castor-save to stop transient build failures |
Change #1310184 had a related patch set uploaded (by Vaughn Walters; author: Vaughn Walters):
[integration/config@master] jjb: [catalyst-daily-*] Replace castor-save to stop transient build failures
Change #1310184 merged by jenkins-bot:
[integration/config@master] jjb: [catalyst-daily-*] Replace castor-save to stop transient build failures