On Tue, Oct 22, 2019 at 1:48 PM Ullrich Hafner wrote:
> If the TaskListenerDecorator method might be called on the agent how can I
> transfer results back to the master from it?
Really best to look at the example implementation in `TimeoutStep` to
see how to use `Channel.export`.
> Or is the
> Am 22.10.2019 um 15:20 schrieb Jesse Glick :
>
> On Tue, Oct 22, 2019 at 5:44 AM Ullrich Hafner
> wrote:
>>.withContext(new ConsoleLogSplitter(…)) // implements
>> TaskListenerDecorator and writes the output to a temporary file
>>
On Tue, Oct 22, 2019 at 5:44 AM Ullrich Hafner wrote:
> .withContext(new ConsoleLogSplitter(…)) // implements
> TaskListenerDecorator and writes the output to a temporary file
> .withCallback(new RecordIssuesCallback(…)) // extends
>
I finally managed it to implement a block scoped step. Currently I invoke the
body of the step using this API
getContext().newBodyInvoker()
.withContext(new ConsoleLogSplitter(…)) // implements
TaskListenerDecorator and writes the output to a temporary
On Mon, Jan 14, 2019 at 6:34 PM Ullrich Hafner wrote:
> Which API can I use to read the individual console log information of a
> parallel stage?
There is not an API exactly for that, but you can use various
techniques in `workflow-api` like `FlowScanner` to get the set of
`FlowNode`s in the
If a pipeline contains parallel stages, then the console log will contain an
unordered mix of stdout messages of all parallel stages. This makes it
impossible to decided which log message is from which parallel stage if I
access the log using Run.getLogReader().
Since a couple of weeks the
