Page MenuHomePhabricator

Add experimental blubber test build/run to mathoid jenkins test pipeline
Closed, ResolvedPublic

Description

Currently when a mathoid patch is submitted by a trusted user, the test npm-node-6-jessie is triggered. As part of the build pipeline project, we will likely want to replace that with a run of the test container built by Blubber. The first step for this is likely to create an experimental job that runs as part of test to build and run the blubber container. Once this test proves reliable and expedient then we can replace the existing npm-node-6-jessie job.

We should be mindful that we don't increase the average test pipeline time for mathoid as part of this process.

Event Timeline

thcipriani triaged this task as Medium priority.

@dduvall already has a good start here, reassigning.

Change 388546 had a related patch set uploaded (by Thcipriani; owner: Thcipriani):
[integration/config@master] SSD: Add npm-service-pipeline experimental job

https://gerrit.wikimedia.org/r/388546

Change 388546 merged by jenkins-bot:
[integration/config@master] Add service-pipeline-test-only experimental job

https://gerrit.wikimedia.org/r/388546

Change 391136 had a related patch set uploaded (by Dduvall; owner: Dduvall):
[integration/config@master] Added trigger-service-pipeline jobs

https://gerrit.wikimedia.org/r/391136

Change 391136 merged by jenkins-bot:
[integration/config@master] Added trigger-service-pipeline jobs

https://gerrit.wikimedia.org/r/391136

Change 392871 had a related patch set uploaded (by Thcipriani; owner: Thcipriani):
[mediawiki/services/mathoid@master] Add blubber.yaml

https://gerrit.wikimedia.org/r/392871

Change 392871 merged by jenkins-bot:
[mediawiki/services/mathoid@master] Add blubber.yaml

https://gerrit.wikimedia.org/r/392871

Those trigger-* jobs were merely a workaround which should have been addressed by upgrading a Jenkins plugin T271683. I will look at removing them via T271107.