From a44053b0a1ac357eb63f9ebc2eed159cf7634cc5 Mon Sep 17 00:00:00 2001 From: surtur Date: Tue, 22 Mar 2022 16:08:34 +0100 Subject: [PATCH] add "tmate-enabled Drone runners" article fixes https://git.dotya.ml/dotya.ml/community/issues/37 --- .../user/drone/tmate-enabled-drone-runners.md | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 content/docs/user/drone/tmate-enabled-drone-runners.md diff --git a/content/docs/user/drone/tmate-enabled-drone-runners.md b/content/docs/user/drone/tmate-enabled-drone-runners.md new file mode 100644 index 0000000..91be78a --- /dev/null +++ b/content/docs/user/drone/tmate-enabled-drone-runners.md @@ -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 Brad.