[workflow plugin] is there a way to get workflow node steps to show in node history?

[Kevin]

Title says it all, is there a way to get workflow node steps to show in node history?  At least for me the node steps in the CPS DSL don't appear to do this.

I've got a one-shot cloud provider that inspects history as a last resort (with a RetentionStrategy) in case a RunListener isn't called, additionally it would be nice if history showed these steps anyways imho.

[Kevin]

Actually now that I look a things more closely it looks like the actual node-steps don't call RunListeners either, is it possible to have the "one shot" slave behavior in a workflow?  If so how?

[Kohsuke Kawaguchi]

I'm not sure if I understand the question.

I guess you want to know what has run on a given hudson.model.Node? When the only things that run on Node was hudson.model.Run, RunListener was sufficient to keep track of this, but with workflow, we are running PlaceholderTask on Executor, and there's currently no Listener to get notified for that?

Would ExecutorListener of some use? Or am I missing the question?

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/83d5b6aa-78d5-49a2-9f66-9d3cf46ccc94%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Kohsuke Kawaguchi

[Kevin Browder]

Basically I'm trying to replace a bunch of jobs that are in one-shot vms (that get removed after a while with a RetentionStrategy and get taken offline after a single run with a RunListener) and combine them into a single workflow, ideally the same behavior would apply.

Seems like swapping my RunListener out for an ExecutorListener would work fine for this use case.

You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/yJ4fxgHNRf4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAN4CQ4x_XSL1S3WFF_iNEH9b9tuxZ3hEAsrSQXRQZvPn%2BZu_7A%40mail.gmail.com.

[Jesse Glick]

On Tuesday, December 16, 2014 10:39:22 PM UTC-5, Kevin wrote:

Seems like swapping my RunListener out for an ExecutorListener would work fine for this use case.

That would help, though it does not handle flows crossing Jenkins restarts. You are advised to use OnceRetentionStrategy from durable-task-plugin for this purpose, or otherwise check for ContinuableExecutable from an existing retention strategy.

Out of curiosity, which cloud is this? It would be nice to update workflow-plugin/COMPATIBILITY.md with a link to any related issue marked with the ‘workflow’ label.

[Kevin]

OK great, I'll try out OnceRetentionStrategy too thanks.

The cloud we use isn't anything that's open sourced at present, just a little plugin I whipped up for our in house virtualization infrastructure.  Can't really say to much more than that at present, but I hope to have a whitepaper on our infrastructure sometime this half-year so I should be able to share much more then.

Anyways, neat stuff, keep up the good work!