GSoC Candidates has expressed that they would really like a testing environment for T175768. Indeed, our past live-testing probably wont scale when it comes to doing mass-changes like replacing an underlying kubernetes library.
|Resolved||None||T175768 Improvements for the Toolforge 'webservice' command|
|Resolved||None||T190884 Replicate toolforge 'webservice' setup in toolsbeta|
|Resolved||zhuyifei1999||T190893 Setup the webservice-related instances in toolsbeta|
|Resolved||Andrew||T190895 Request increased quota for toolsbeta|
|Resolved||zhuyifei1999||T192618 Can't ssh into new instance created at toolsbeta|
|Resolved||Andrew||T190896 Request addition to 'toolsbeta.admin' service group|
Next question: considering that the docker containers contains the webservice code, which are subject to modification for the parent task, is it necessary to separate toolsbeta's aptly and docker-builder from toolforge's?