dotya.ml/ docs
2
0
Fork 0
Code Issues 1 Pull Requests Releases Activity

add "tmate-enabled Drone runners" article
All checks were successful
continuous-integration/drone/push Build is passing
Details 

fixes dotya.ml/community#37
This commit is contained in:
surtur 2022-03-22 16:08:34 +01:00
parent 587b85f36b
commit a44053b0a1
Signed by: wanderer
GPG Key ID: 19CE1EC1D9E0486D
1 changed files with 24 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
content/docs/user/drone/tmate-enabled-drone-runners.md Normal file
View File

@ -0,0 +1,24 @@
---
title: "tmate-enabled Drone runners"
date: 2022-03-22T15:41:06+01:00
draft: false
---
#### tl;dr
The gist is that a pipeline *can* be (re)started (usually, only failed pipelines
are manually restarted, hoping for a better result as if the error was floating
somewhere around the Ether and not our code most of the times) in *debug* mode.
After a pipeline fails in said debug mode, a `tmate` client connection to a
[`tmate`](https://tmate.io/) server (as configured in the `drone` server
configuration files -
[ref](https://git.dotya.ml/dotya.ml/drone/commit/e6e2a0233e00874ecd859435aee76f0a01286063))
is open from withing the container that the failing *step* was running in and
connection instructions for `ssh`-ing are displayed.
The error can then be debugged more intimately in the precise environment that made the bug appear.
#### conclusion
Instead of repeating any more of what's already been said, I suggest anybody
interested reads the original
[kind-of-reference](https://discourse.drone.io/t/feature-preview-debug-mode/8344)
post by <abbr title="one of the authors of Drone CI">Brad</abbr>.