On Wed, May 20, 2020 at 8:39 AM Gerald Wiltse wrote:
>
> it still captures the problem with visuals, and helps demonstrate demand for
> a solution.
When we were using Build Flow before the creation of Pipeline, my
users really liked the visualization provided by the buildgraph-view
plugin. I
Upon further review, this uses an observer pattern which is just completely
different from what I was envisioning. I'm still glad I found it because it
still captures the problem with visuals, and helps demonstrate demand for a
solution.
Gerald R. Wiltse
jerrywil...@gmail.com
On Wed, May 20,
It's worth noting that I think a lot of good code and abstraction and
capturing of the problem already exists here:
https://plugins.jenkins.io/join/
I'm not sure if Stefan Wolf still watches this list or actively contributes
to Jenkins, but his insight would probably be invaluable. I will study
I find this feedback very encouraging. It definitely does seem to be a good
candidate for JEP proposal. I will plan for that in the mid-term future.
Your suggestions about alternatives are all right on. In one large
environment, I created a solution with a metajob that received webhooks
from all
As far as I know there is no serious work in progress in this area,
and no particular plan for work on it from the “core team” (maybe a
misleading phrase).
Indeed `DependencyGraph` as currently defined is very rigid and could
not work well even for moderately subtle Pipeline scenarios, so it
does
TLDR;
This ticket suggests that Jenkins team open a discussion and planning to
spend significant times on the problems mentioned above. If you have
experienced issues with diamond dependencies between jenkins jobs, or want
more features around upstream() and downstream() dependency handling,
