I already did that, see https://github.com/lance513/job-fan-in-plugin/tree/pipelineSupport. Creating a PR to the plugins master branch on jenkinsci is on my list right after I can release Pipeline support for the Dependency Graph View Plugin (see https://github.com/jenkinsci/depgraph-view-plugin/pull/16).
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, 19. February 2019 20:10, Gerald Wiltse <[email protected]> wrote: > Thank you for the confirmation. Now onto the hard problem of actually > replicating this functionality with "Pipeline". > > On Tuesday, February 19, 2019 at 9:31:30 AM UTC-5, Daniel Beck wrote: > >>> On 19. Feb 2019, at 04:05, Gerald Wiltse <[email protected]> wrote: >>> >>> I ask because the wiki for the JobFanIn plugin says this: "This plugin can >>> be used with Build Pipeline, Delivery Pipeline etc.", yet is based on all >>> of the aforementioned API's. >>> >> >> https://plugins.jenkins.io/build-pipeline-plugin >> https://plugins.jenkins.io/delivery-pipeline-plugin >> >> This confusion resulting from the rename of Workflow to Pipeline was >> considered acceptable when the decision was made :( -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/rH7V49zhkp8KhqmJkZJdLSDcVSyE2KSi-q-mpbS2qirXnIkwGs4Jv_-kAYPdou1c753WZngXei9GNvq4d4p-h5Hi_RXkNadS_yjA0-PSfnQ%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
