2015-02-26 17:09 GMT+01:00 Les Mikesell <[email protected]>: > On Thu, Feb 26, 2015 at 8:41 AM, Jesse Glick <[email protected]> wrote: > > On Thursday, February 12, 2015 at 10:43:28 AM UTC-5, LesMikesell wrote: > >> > >> With workflow, if you trigger another build, how do you access that > >> other build object? For example to find the build number so you can > >> copy its artifacts into the workflow job. Or find the SVN_REVISION > >> so you can trigger other builds of that same revision? > > > > > > This area is still relatively weak in Workflow, so I plan to add more > > features here. > > > > https://issues.jenkins-ci.org/browse/JENKINS-26100 > > https://issues.jenkins-ci.org/browse/JENKINS-25851 > > > > Is there some reason workflow isn't just a superset of build flow, >
The explanation you ask for has already been given here and there on the ML. IIRC, Build flow plugin has been deemed a dead-end by its creator (Nicolas De Loof, IIRC). That always happens in our field. But that experience has somehow also served as another feedback to create a far broader-scoped plugin. > adding control of workspaces and inlining? What's the point of > having open source if everyone starts over from scratch whenever they > have a new idea anyway? Or, why aren't both of these just class > libraries for the groovy plugin with an easy way to add new ones for > common high-level operations? > Many reasons already given I guess (suspendable, etc.) -- 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/CANWgJS6HtahhrgKhzPNkzzzOU3NbRk0XAA_VME1PRFXnbEZtDw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
