On Thursday, January 15, 2015 at 3:58:07 AM UTC-5, James Nord wrote: > > Plugins must be aware of the workflow plugin and implement some code for > it. >
https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md There are of course some cases where the functionality of the plugin is unnecessary in a workflow because you can just express the desired logic directly in your script. Integrations are needed for plugins which expose true features (rather than workarounds for limitations of freestyle projects). It seems like in this case the functionality is real and needs an integration, since you would want to do configuration on the node, and may have external tools using CLI or REST to update the status of specific nodes. So it would make sense to file an RFE for the plugin to add a Workflow step (probably block-scoped, so the lock release is implicit); add the ‘workflow’ label and mention in COMPATIBILITY.md. -- 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/876f2bbc-5801-4311-aa03-153e7ca82057%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
