This epic covers the 2018 MVC deliverable scope for Interactive Web Terminals ### Problem to solve CI/CD jobs are executed by runners based on the configuration provided by users in their pipeline definition. But this execution is not interactive and, in case of failure, users cannot dig into details to spot the possible source of the problem. When a test fails, users may want to inspect files and to run commands. This is a huge improvement to the current status, where output is the only feedback they get. If we make the session where the job has been executed live, users can access it and get what they need. This could be something similar to what we already have to inspect deployments (https://docs.gitlab.com/ee/administration/integration/terminal.html) ### Plan The 11.3 release adds a functioning interactive terminal for k8s and shell executors (via https://gitlab.com/gitlab-org/gitlab-ce/issues/50144), then Docker support (available in .com) is added in 11.4 via https://gitlab.com/gitlab-org/gitlab-terminal/issues/3 and https://gitlab.com/gitlab-org/gitlab-runner/issues/3467. -  ### Links / Reference - https://gitlab.com/gitlab-org/gitlab-ce/issues/25990 is the original meta issue for this change and contains historical conversations regarding the solution but does not represent a current, accurate source of truth. - An epic containing stories for future improvement (as of yet unscheduled) can be found at https://gitlab.com/groups/gitlab-org/-/epics/338.