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. On Tuesday, December 16, 2014, Kohsuke Kawaguchi <[email protected]> wrote: > 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? > > > 2014-12-16 7:00 GMT-08:00 Kevin <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>>: >> >> 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? >> >> On Monday, December 15, 2014 4:39:53 PM UTC-5, Kevin wrote: >>> >>> 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. >>> >> -- >> 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 [email protected] >> <javascript:_e(%7B%7D,'cvml','jenkinsci-users%[email protected]');> >> . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/83d5b6aa-78d5-49a2-9f66-9d3cf46ccc94%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-users/83d5b6aa-78d5-49a2-9f66-9d3cf46ccc94%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > Kohsuke Kawaguchi > > -- > 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 > [email protected] > <javascript:_e(%7B%7D,'cvml','jenkinsci-users%[email protected]');> > . > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/CAN4CQ4x_XSL1S3WFF_iNEH9b9tuxZ3hEAsrSQXRQZvPn%2BZu_7A%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CAN4CQ4x_XSL1S3WFF_iNEH9b9tuxZ3hEAsrSQXRQZvPn%2BZu_7A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMqyT3Yex5PaqF0Wk_1cv1A6uJTpqWbQwwiPKW_07Z%2BNXZj0qg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
