Interactive Web Terminals
Interactive web terminals give the user access to a terminal in GitLab for
running one-off commands for their CI pipeline. You can think of it like a method for
debugging with SSH, but done directly from the job page. Since this is giving the user
shell access to the environment where GitLab Runner
is deployed, some security precautions were
taken to protect the users.
Two things need to be configured for the interactive web terminal to work:
Interactive web terminals are partially supported in Support for fixing these limitations is tracked in the following issues:
Sometimes, when a job is running, things don’t go as you would expect, and it
would be helpful if one can have a shell to aid debugging. When a job is
running, on the right panel you can see a button When clicked, a new tab opens to the terminal page where you can access
the terminal and type commands like a normal shell.
If you have the terminal open and the job has finished with its tasks, the
terminal blocks the job from finishing for the duration configured in
Read the Web IDE docs to learn how to run Interactive Terminals through the Web IDE.
Configuration
[session_server]
configured
properly
Partial support for Helm chart
gitlab-runner
Helm chart.
They are enabled when:
loadBalancer
service
Debugging a running job
docker
executor does not keep running
after the build script is finished. At that point, the terminal automatically
disconnects and does not wait for the user to finish. Please follow this
issue for updates on
improving this behavior.debug
that opens the terminal
for the current job.
[session_server].session_timeout
until you
close the terminal window.
Interactive Web Terminals for the Web IDE