-
Notifications
You must be signed in to change notification settings - Fork 670
Bug 1801857: Cleanup Pipeline Builder #4240
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
Bug 1801857: Cleanup Pipeline Builder #4240
Conversation
75e3e2a to
d93857b
Compare
serenamarie125
left a comment
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.
Still seeing the column headers when there are no pipeline parameters and resources. Unsure if that is part of another fix?
serenamarie125
left a comment
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.
wow i'm impressed, really nice job with this Andrew! Look forward to looking at it in detail soon
@serenamarie125 Yup, see #4180 |
d93857b to
5b5f7c6
Compare
Thanks @serenamarie125 - I've just pushed another commit to try and fix the odd balance of padding around the visualization. Not sure why, but the layout engine has some odd padding on the top and left that it didn't have when I originally did this work pre-ff. Hopefully we get a good run down tomorrow and shake out the last few things that are a bit odd in the UX department. |
...ole/src/components/pipelines/detail-page-tabs/pipeline-details/PipelineVisualizationTask.tsx
Outdated
Show resolved
Hide resolved
...ole/src/components/pipelines/detail-page-tabs/pipeline-details/PipelineVisualizationTask.tsx
Outdated
Show resolved
Hide resolved
|
@andrewballantyne Ran this locally and it works well. Just left comments at two places where variable naming could be more descriptive. This takes care of the earlier issues. However, I just felt the connectors are a bit confusing. |
|
/test analyze |
|
@abhinandan13jan I discussed this with @serenamarie125 - it will likely be a limitation for the first pass of the Pipeline Builder. We had talked about an "advanced" mode but we decided to keep it to the straight 3 actions (all of which will not connect disconnected paths). |
5b5f7c6 to
b5e3c9e
Compare
|
Resource selection issue is related to the fix Rohit is doing in #4266 |
frontend/packages/dev-console/src/components/pipelines/pipeline-topology/factories.ts
Outdated
Show resolved
Hide resolved
|
@andrewballantyne: This pull request references Bugzilla bug 1801857, which is invalid:
Comment DetailsIn response to this:
Instructions 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. |
|
/bugzilla refresh |
|
@andrewballantyne: This pull request references Bugzilla bug 1801857, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions 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. |
|
/lgtm |
b5e3c9e to
202a761
Compare
202a761 to
5ea443a
Compare
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.
Why don't you use a flex layout and align items center?
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.
Why the cast?
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.
Hold over from the previous design I was working with... there was a type error I couldn't figure out, so I casted it to get around it.
Removing
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.
Use consistent names / values.
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.
| {inputResources && inputResources.map(renderResource('inputs'))} | |
| {inputResources.map(renderResource('inputs'))} |
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.
| {outputResources && outputResources.map(renderResource('outputs'))} | |
| {outputResources.map(renderResource('outputs'))} |
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.
Why aren't you using the formik fields we have for this?
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 need to do custom save logic and Formik messing with the value directly caused desync issues with the errors + updating of the values. I figured I'd just manage all things Task related and let Formik manage the form items (name, params, resources on the main page).
I suspect I could find a way to make the logic exist in the yup schema... but I have not yet tackled that.
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.
why & {} ?
Can it contain any field with any value?
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 don't think {} means anything special... it just means an empty object (no key/values). Which in large is useless... I'll remove it.
It was a hold over from when I didn't have PipelineBuilderTaskBase that contained common items. I just never removed it when I was cleaning it up.
fab3489 to
1cbfd98
Compare
2f4f0f6 to
6dfc737
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinandan13jan, andrewballantyne, christianvogt The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@andrewballantyne: All pull requests linked via external trackers have merged. Bugzilla bug 1801857 has been moved to the MODIFIED state. DetailsIn response to this:
Instructions 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. |







Fixes:
https://issues.redhat.com/browse/ODC-2854
Analysis / Root cause:
Pipeline Builder landed in a really rough shape, this PR should clean up a lot of the issues and serve to enable it again in the UI.
Solution Description:
Lots of cleanup and consolidation happened with this fix.
Screen shots / Gifs for design review:
cc @openshift/team-devconsole-ux
Unit test coverage report:
Unit tests still to come (may come in a different PR for ease of reviewing)
Test setup:
Pipeline Operator is needed, but otherwise entering through the "create pipeline" button on the Pipeline list page is all you need to do.
Browser conformance: