Project | Branch | Lines +/- | Subject | |
---|---|---|---|---|
integration/config | master | +7 -4 | pipeline: Schedule trigger jobs on master node | |
integration/config | master | +4 -4 | jjb: Run trigger jobs on contint1001 agent directly |
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | MoritzMuehlenhoff | T241719 Migrate remaining self-hosted puppet masters to Puppet 5 / facter 3 | |||
Resolved | Jdforrester-WMF | T236576 Move all Wikimedia CI (WMCS integration project) instances from jessie to stretch | |||
Resolved | Jdforrester-WMF | T247109 Replace integration-trigger-01 with running the dummy job on contint1001 agent |
Event Timeline
Mentioned in SAL (#wikimedia-releng) [2020-03-06T19:05:55Z] <James_F> Manually pushing trigger-helloworldoid-pipeline-test over to contint1001 to test T247109
Change 577647 had a related patch set uploaded (by Jforrester; owner: Jforrester):
[integration/config@master] jjb: Run trigger jobs on contint1001 agent directly
Change 577647 merged by jenkins-bot:
[integration/config@master] jjb: Run trigger jobs on contint1001 agent directly
This effectively limits the number of concurrent pipelinelib based jobs to 3 since contint1001 is configured with just 3 executors. Another approach we might take is to create a dummy node for trigger jobs that uses a second ssh connection to contint1001 (different user maybe) and has more executors assigned. The only concern there is that contint1001 would be allocating memory for a jenkins agent that does nothing.
Change 577678 had a related patch set uploaded (by Dduvall; owner: Dduvall):
[integration/config@master] pipeline: Schedule trigger jobs on master node
Reopening for follow-up patch review that schedules trigger builds on the master node.
Mentioned in SAL (#wikimedia-releng) [2020-03-06T22:42:18Z] <James_F> Raised executor count on contint1001 from 3 to 12 for T247109
Change 577678 abandoned by Dduvall:
pipeline: Schedule trigger jobs on master node
Reason:
Scheduling on master is unacceptable
We should have the instance integration-trigger-01.integration.eqiad.wmflabs deleted via Horizon and then remove it from the CI Jenkins ( https://integration.wikimedia.org/ci/computer/integration-trigger-01/ ).
The instance has been shutoff pending deletion. https://openstack-browser.toolforge.org/server/integration-trigger-01.integration.eqiad.wmflabs
Mentioned in SAL (#wikimedia-releng) [2020-05-01T18:43:21Z] <James_F> Deleting integration-trigger-01 from WMCS for T247109