0 views collected around this technical thread.
This article explains how to run a Shell script within a Jenkins pipeline, capture its output, and present it through the Input step as a multi‑line text field for approval, illustrating the process with complete pipeline examples.
This article narrates the step‑by‑step design of a workflow engine, starting with a linear approval chain and progressively adding parallel, conditional, nested, proxy, timing, and scripting capabilities, illustrating how each new requirement reshapes the underlying tree‑structured state machine.
This article narrates the step‑by‑step evolution of a custom workflow engine, detailing how simple sequential approvers were transformed into a tree‑structured system supporting parallel, multi‑sign, conditional, delegation, and nested nodes, complete with status management and progress metrics.
This article narrates the step‑by‑step evolution of a workflow engine, starting with a basic sequential approver list and progressively adding countersign, parallel, conditional, delegation, timeout, scripting, and nesting capabilities, illustrating a tree‑based architecture and node‑state management for robust backend process automation.
This article walks through the step‑by‑step design of a workflow engine, starting with a basic approval chain and progressively adding countersign, parallel, conditional, delegation, timeout, scripting, and progress‑tracking features, illustrating a tree‑based architecture and node‑state management.
The article narrates the progressive design of a customizable workflow engine, starting from a simple linked‑list approver chain and evolving through countersign, parallel, conditional, delegation, timeout, progress‑percentage, and script‑hook features, illustrating each stage with node classifications, state definitions, and tree‑based structures.
The article chronicles the step‑by‑step evolution of a custom workflow engine, detailing how sequential approvals, countersign, parallel, conditional, delegation, timeout, rejection, nesting, and scripting features were incrementally added to support increasingly complex business processes.
The article walks through the step‑by‑step evolution of a custom workflow engine, starting with a basic linked‑list approver chain and progressively adding support for parallel, multi‑sign, conditional, timed, proxy, cancellation, pre‑/post‑conditions, progress metrics, and script hooks, illustrating a comprehensive backend design.