|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|
|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|
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.
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/ ).