Skip to content
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

Removes Pipeline Graph alignment setting #9425

Conversation

andrewballantyne
Copy link
Contributor

Fixes:
https://issues.redhat.com/browse/ODC-5100

Analysis / Root cause:
Our current layout algorithm for Pipeline Topology is called Dagre. Dagre lays out our graph in such a fashion that goes from one side to another (in our case left to right). The problem we had was it was built to try and mimic the previous column-layout which in itself had several layout problems (couldn't do complex graphs).

Solution Description:
Removed the 'top left' alignment from the Dagre layout in order to go with a more middle-vertical alignment. This doesn't "solve" all the problems, but it makes it more balanced.

There are still several issues with the layout, and after trying to tweak them, I am fairly confident there is little we can do with our current Dagre layout and not get into a wack-a-mole of problem solving layout issues.

Screenshots at the bottom as they are many.

Unit test coverage report:
None, we don't have tests for Dagre layouts. Although some though in this area probably wouldn't hurt (not sure of a clean deterministic way of testing).

Test setup:

Used these pipelines

Browser conformance:

  • Chrome
  • Firefox
  • Safari
  • Edge

Screenshots:

Screen Shot 2021-07-06 at 6 42 55 PM
Screen Shot 2021-07-06 at 6 43 02 PM
Screen Shot 2021-07-06 at 6 43 09 PM
Screen Shot 2021-07-06 at 6 43 15 PM
Screen Shot 2021-07-06 at 6 43 21 PM
Screen Shot 2021-07-06 at 6 43 27 PM
Screen Shot 2021-07-06 at 6 43 34 PM
Screen Shot 2021-07-06 at 6 43 39 PM
Screen Shot 2021-07-06 at 6 43 51 PM
Screen Shot 2021-07-06 at 6 43 56 PM
Screen Shot 2021-07-06 at 6 44 03 PM
Screen Shot 2021-07-06 at 6 44 10 PM
Screen Shot 2021-07-06 at 6 44 17 PM
Screen Shot 2021-07-06 at 6 44 25 PM
Screen Shot 2021-07-06 at 6 44 37 PM
Screen Shot 2021-07-06 at 6 44 46 PM
Screen Shot 2021-07-06 at 6 44 52 PM
Screen Shot 2021-07-06 at 6 44 59 PM
Screen Shot 2021-07-06 at 6 45 06 PM
Screen Shot 2021-07-06 at 6 45 13 PM
Screen Shot 2021-07-06 at 6 45 20 PM
Screen Shot 2021-07-06 at 6 45 26 PM
Screen Shot 2021-07-06 at 6 45 34 PM
Screen Shot 2021-07-06 at 6 45 43 PM

@openshift-ci openshift-ci bot added component/pipelines Related to pipelines-plugin approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jul 6, 2021
@karthikjeeyar
Copy link
Contributor

Verified locally, looks good to me.
/lgtm

Adding hold, so it doesn't get merged before @bgliwa01 looks at the changes.
/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 7, 2021
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 7, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 7, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andrewballantyne, karthikjeeyar

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@christianvogt
Copy link
Contributor

fyi @siamaksade @serenamarie125

@karthikjeeyar
Copy link
Contributor

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 12, 2021
@openshift-merge-robot openshift-merge-robot merged commit 66f7e51 into openshift:master Jul 12, 2021
@spadgett spadgett added this to the v4.9 milestone Jul 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. component/pipelines Related to pipelines-plugin lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants