This has several sub tasks:

A) we have to create Jenkins jobs and have them triggered. It is an excellent opportunity to level up another team member to how we are using Jenkins to push code on the beta cluster and how we define jobs in Jenkins Job Builder.

B) configure Multiversion for which I definitely use a refresh / crash course. I am fairly outdated there, definitely willing to do the grunt work under supervision of someone more used to it.

C) Have the nightly.wmflabs.org domain created and adjust configuration files in puppet (such as Varnish files). Most are variance of the top level domain name with prod => '.org', labs => 'beta.wmflabs.org'. That would need to sync up with Varnish ops.

In T1112#19337, @hashar wrote:

This has several sub tasks:

A) we have to create Jenkins jobs and have them triggered. It is an excellent opportunity to level up another team member to how we are using Jenkins to push code on the beta cluster and how we define jobs in Jenkins Job Builder.

This task :) Feel free to edit description. I also fully support the leveling up idea.

B) configure Multiversion for which I definitely use a refresh / crash course. I am fairly outdated there, definitely willing to do the grunt work under supervision of someone more used to it.

T805 - Assigned to Reedy :)

C) Have the nightly.wmflabs.org domain created and adjust configuration files in puppet (such as Varnish files). Most are variance of the top level domain name with prod => '.org', labs => 'beta.wmflabs.org'. That would need to sync up with Varnish ops.

T1111 - assigned to Reedy :)

Bah I should have commented on the tracking task T426. Thank you Greg.