-
Notifications
You must be signed in to change notification settings - Fork 667
Pipeline Topology Implementation #4004
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pipeline Topology Implementation #4004
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@serenamarie125 I took a causal stab at solving https://issues.redhat.com/browse/ODC-1860 when I stumbled upon the issue in my work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I likely can gut a lot of this too... I just haven't looked too much into it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jeff-phillips-18 This is the hack we discussed - we need to find a better way for me to get a notification when the layout finishes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All changes for DagreLayout were rushed and not really thought through. @jeff-phillips-18 @christianvogt Feel free to comment on direction / changes. I'll likely conflict with your work Jeff when it comes to your topology work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can reconcile once the changes are in, you can use the GRAPH_LAYOUT_END_EVENT event once its there.
725260d to
c7e7a44
Compare
c7e7a44 to
b745f71
Compare
|
@andrewballantyne this is looking really good! will this PR also cover the tooltips associated with the PLR visualization? I'm assuming they shouldn't be affected, but you never know :) Is it also worth including screenshots of what the PL vs PLR visualizations look like? |
Doh, of course, I'll update with it. I tested it under the hood but didn't post the screenshots 😦 Not sure what I was thinking haha. |
|
@serenamarie125 Apologizes for that; Pipeline Runs have been added to the description (from the Pipeline Run details page). |
b745f71 to
5f923f2
Compare
|
/test backend |
|
/retest |
1 similar comment
|
/retest |
|
/hold |
|
/hold cancel |
|
@andrewballantyne: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
| endPoint.clone().translate(-targetNode.getBounds().width / 2, 0), | ||
| )} | ||
| stroke="var(--pf-global--BorderColor--light-100)" | ||
| fill="none" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rather these styles be in a .scss file but ok.
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: andrewballantyne, jeff-phillips-18 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Folded into #4055 for CI sanity. |
Fixes:
https://issues.redhat.com/browse/ODC-2605
Analysis / Root cause:
Implements the foundation of the Pipeline Builder and replaces the existing rendering logic to be more inline with what the Pipeline spec can present as a node network.
Solution Description:
Pulled the
@console/topologycode into Pipelines. This gives us the power of a layout engine and a free and open canvas to draw in.Screen shots / Gifs for design review:

@openshift/team-devconsole-ux
Note: the top visualization is the same rendering issue from https://issues.redhat.com/browse/ODC-2464 fixed.
There are some unexpected outcomes out of the layout as of right now:
I have no current intent on addressing the above issues until after the Pipeline Builder feature is completed. We'll likely need to work on a constraint system with Dagre which may use "ghost" groups or something (unsure of the solution at this time).
Pipeline Runs:
Unit test coverage report:
Test setup:
frontend/packages/dev-console/yamls/pipelines/install_pipeline_mocks.shor create / upload your own)Browser conformance:
/kind feature
cc @jeff-phillips-18 @christianvogt