Skip redundant setup steps in Remote development workspace
Overview
The following discussion from !3717 (merged) should be addressed:
-
@splattael started a discussion: (+1 comment) Question (non-blocking)
I saw that we have
skip_setup
for GitLab Shell and Workhorse as well:support/templates/makefiles/gdk-config.mk.erb 19:gitaly_skip_setup = <%= config.gitaly.skip_setup? %> 59:gitlab_shell_skip_setup = <%= config.gitlab_shell.skip_setup? %> 106:workhorse_skip_setup = <%= config.workhorse.skip_setup? %>
Can we skip them too for Remote Development?
Impacted categories
The following categories relate to this issue:
-
gdk-reliability - e.g. When a GDK action fails to complete. -
gdk-usability - e.g. Improvements or suggestions around how the GDK functions. -
gdk-performance - e.g. When a GDK action is slow or times out.
Steps to replicate (optional)
Proposal (optional)
Environment (optional)
- Operating system name:
<!-- output of `uname -a` command -->
- Architecture:
<!-- output of `arch` command -->
- The contents of your
gdk.yml
(if any) - Ruby version:
<!-- output of `ruby --version` command -->
- GDK version:
<!-- output of `git rev-parse --short HEAD` command -->