14.6 Runner team iteration plan
The details in this issue cover the top priority work items for the Runner team for the 14.6 release.
🏚
Tech Debt -
@ajwalker
&&@tmaczukin
Update used Go version to 1.17.x -
@ggeorgiev_gitlab
Command injection via branch name in CI pipelines🔒
🏃
Runner Core
🐛
Bugs -
@ajwalker
missed:14.6 PWSH Executor fails to terminate on job failure priority1 documentation missed:14.6 -
@ajwalker
~"missed-SLO" missed:14.6 Only parse stdout while determining uid when FF_DISABLE_UMASK_FOR_DOCKER_EXECUTOR is enabled' [FY22-Q4 OKR GOAL] documentation -
@deastman
~"missed-SLO" "409 Conflict" causes Runner to not run any jobs, and give up checking for new jobs for half an hour [FY22-Q4 OKR GOAL]
Features
-
@ggeorgiev_gitlab
missed:14.6 FIPS Compliance for GitLab Runner - iteration 1 (FY22-Q4 CPO/CTO OKR) documentation -
@ratchade
missed:14.2 missed:14.3 missed:14.4 Kubernetes should use a scheduled cleaner to ensure all related resources are cleaned up -
@ratchade
missed:14.3 missed:14.4 Old Runner pods hanging around, eventually block new pods from starting [FY22-Q4 OKR GOAL] -
@ratchade
missed:14.6 Add interactive web terminal support to GitLab Runner Helm Chart documentation -
@ratchade
missed:14.6 Add support for Windows Server, version 2022 blocked documentation -
@pedropombeiro
Have gitlab_runner_jobs in response all the time documentation -
@ajwalker
missed:14.6 Proper context cancelation for after_script/graceful cancels in scripts documentation -
@ggeorgiev_gitlab
missed:14.5 missed:14.6 GitLab Runner Operator for OpenShift- Power9 architecture-ppc64le documentation
☁
Runner SaaS No new features planned ship in this category in 14.6
-
macOS beta is ongoing. -
@tmaczukin
Idle Scaling Factor -
@tmaczukin
Create the GitLab Saas Runner Scaling architectural blueprint
🎢
Runner Fleet This category is responsible for delivering a lovable user experience for customers that manage a fleet of runners.
- maintainers of a group that manage a fleet of runners for their group/namespace (GitLab SaaS or Self-Managed)
- administrators of a GitLab instance that manage a fleet of runners for their organization.(Self-Managed)
Theme: "The milestone where stale runners became a thing"
-
backend Add new "stale" runner state documentation -
frontend Filter and display stale runners in the UI -
frontend backend Shared Runners setting is being disabled on projects intermittently 🐛 -
frontend Relocate the number of online runners text in toolbar -
frontend Version field overflow IP address at the runner's admin page -
backend Start capturing "executor" from gitlab-runner -
backend Add unit tests to NumbersHelper -
@pedropombeiro
Implement register_group_runner policy -
@pedropombeiro
Implement admin_group_runners policy
✈ 🖌
User Experience Problem validation research workflowproblem validation
Solution validation research workflowsolution validation
Design workflowdesign
-
Runner Vision: Part 2 - CI job queues -
Stretch Improve Admin runners list view empty state when there are no registered runners
🔍
Quality Nothing to ship in this category. Capturing the work planned to improve quality.
Edited by Darren Eastman