13.7 Runner team iteration plan
The details in this issue cover the top priority work items for the Runner team for the 13.7 release. The 13.6 release was the first milestone where we introduced the use of a planning issue to augment the Runner team Kanban board.
- The goal is to simplify communication with all stakeholders regarding the team's key focus areas for each milestone iteration.
- This is approximately a 4-week iteration with the Runner code freeze on December 7, 2020.
Must-Ship
Runner Core
-
@ggeorgiev\_
GitLab Runner for Red Hat OpenShift (MVC) -
@tmaczukin
Remove usage of umask 0000 to be secure by default -
@steveazz
Create a pull policy that can fall back on local cache -
@steveazz
Migrate helper image to registry.gitlab.com -
@steveazz
Publish Docker images to ECR public -
@pedropombeiro
Variable inside other variable: Expand variables in Rails by topologically sorting them
Runner Cloud
-
@akohlbecker
macOS Build Cloud (autoscaler): Implement Create for Orka provider -
@akohlbecker
macOS Build Cloud (autoscaler): Implement Delete for Orka provider
Runner Enterprise Management
-
Nothing planned to ship in 13.7. Key goal is to make progress on the UI design for the Automated reset of instance wide runner registration tokens issue.
Slipped from previous release(s)
-
@pedropombeiro
Support Windows Server core, version 2004
Edited by Darren Eastman