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

[UI] deep links to pipeline details page from start page #3086

Merged
merged 15 commits into from
Feb 17, 2020

Conversation

Bobgy
Copy link
Contributor

@Bobgy Bobgy commented Feb 14, 2020

/cc @jingzhang36
/assign @SinaChavoshi
/area frontend

Demo: https://youtu.be/JTTpzSzm_v4


This change is Reviewable

@numerology
Copy link

Thanks @Bobgy ! LGTM as a quick fix. As for a long-term solution, I'm wondering can we stop baking a predefined set of pipelines into our backend server? Instead, we might automatically download pipeline packages automatically when the backend server spin up. Then, IIUC, in resource manager we can get the actual link (which depends on the pipeline ID) and put it on the landing page.

Compile and publish the pipeline packages could be part of the releasing process. I think it may also help us to apply quick fix to samples as well.

WDYT? @IronPan @rmgogogo @jingzhang36

@Bobgy
Copy link
Contributor Author

Bobgy commented Feb 15, 2020

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Bobgy

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

@Bobgy
Copy link
Contributor Author

Bobgy commented Feb 15, 2020

Thanks @Bobgy ! LGTM as a quick fix. As for a long-term solution, I'm wondering can we stop baking a predefined set of pipelines into our backend server? Instead, we might automatically download pipeline packages automatically when the backend server spin up. Then, IIUC, in resource manager we can get the actual link (which depends on the pipeline ID) and put it on the landing page.

Compile and publish the pipeline packages could be part of the releasing process. I think it may also help us to apply quick fix to samples as well.

WDYT? @IronPan @rmgogogo @jingzhang36

Sounds like a good idea to me. Just confirmation, do we also make an extra api endpoint just to query sample ids?

@Bobgy Bobgy added the lgtm label Feb 15, 2020
@Bobgy
Copy link
Contributor Author

Bobgy commented Feb 15, 2020

/retest

1 similar comment
@Bobgy
Copy link
Contributor Author

Bobgy commented Feb 15, 2020

/retest

@Bobgy
Copy link
Contributor Author

Bobgy commented Feb 15, 2020

I'd like to add three more changes:

  1. let frontend import names from a json file
  2. add a presubmit test check to verify names are synced with backend
  3. add simple unit tests for this components.

will update next monday

EDIT: these changes are all done. I think it's relatively safe now. WDUT?

@Bobgy
Copy link
Contributor Author

Bobgy commented Feb 16, 2020

@numerology Can we improve error message of this? I'm not sure what the exception is, it seems it should have more info.
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/kubeflow_pipelines/3096/kubeflow-pipeline-sample-test/1228980064243159041#1:build-log.txt%3A6347

print('error in get_artifact_in_minio: %s', e)

@Bobgy
Copy link
Contributor Author

Bobgy commented Feb 16, 2020

/retest

@rmgogogo
Copy link
Contributor

I'd like to add three more changes:

  1. let frontend import names from a json file
  2. add a presubmit test check to verify names are synced with backend
  3. add simple unit tests for this components.

will update next monday

EDIT: these changes are all done. I think it's relatively safe now. WDUT?

OK. Thanks.

@rmgogogo
Copy link
Contributor

(if this one is hard to be continued, it's also find we just let the link points to the list, just want to save your bandwidth)

@Bobgy
Copy link
Contributor Author

Bobgy commented Feb 17, 2020

(if this one is hard to be continued, it's also find we just let the link points to the list, just want to save your bandwidth)

I think the solution is complete, can you check again?

@numerology
Copy link

Thanks @Bobgy ! LGTM as a quick fix. As for a long-term solution, I'm wondering can we stop baking a predefined set of pipelines into our backend server? Instead, we might automatically download pipeline packages automatically when the backend server spin up. Then, IIUC, in resource manager we can get the actual link (which depends on the pipeline ID) and put it on the landing page.
Compile and publish the pipeline packages could be part of the releasing process. I think it may also help us to apply quick fix to samples as well.
WDYT? @IronPan @rmgogogo @jingzhang36

Sounds like a good idea to me. Just confirmation, do we also make an extra api endpoint just to query sample ids?

IMHO that seems not a p0 requirement at this moment. Anyway no need to make such changes in this PR.

@Bobgy
Copy link
Contributor Author

Bobgy commented Feb 17, 2020

@numerology @renming, thank you for the suggestions. can one of you lgtm?

@rmgogogo
Copy link
Contributor

/lgtm
Thanks. It's hard task.

@k8s-ci-robot k8s-ci-robot merged commit 9b723bf into kubeflow:master Feb 17, 2020
Jeffwan pushed a commit to Jeffwan/pipelines that referenced this pull request Dec 9, 2020
* [UI] deep links to pipeline details page from start page

* Fix

* Update GettingStarted.tsx

* Update GettingStarted.tsx

* Update GettingStarted.tsx

* Adjust format to improve readability

* Use react-testing-library for getting started page tests

* Add error case unit tests

* Frontend import sample config from jsonn and presubmit test to verify configs are synced

* Update presubmit test error message

* Changed to sync only sample_config.json name to frontend

* Improve error message

* Fix tests
magdalenakuhn17 pushed a commit to magdalenakuhn17/pipelines that referenced this pull request Oct 22, 2023
…3086)

* Refactor autoscaler functionality into an interface.

Add no-op autoscaler so users disable creation of autoscaler resources.
Add AutoscalerClassNone feature with test cases

Signed-off-by: jooho <jlee@redhat.com>
Signed-off-by: Dan Sun <dsun20@bloomberg.net>
Signed-off-by: Andrews Arokiam <andrews.arokiam@ideas2it.com>

* Rollback getHPAMetrics to set ScaleTarget,ScaleMetric

Signed-off-by: jooho <jlee@redhat.com>
Signed-off-by: Dan Sun <dsun20@bloomberg.net>
Signed-off-by: Andrews Arokiam <andrews.arokiam@ideas2it.com>

* Fix merge conflict

Signed-off-by: Dan Sun <dsun20@bloomberg.net>
Signed-off-by: Andrews Arokiam <andrews.arokiam@ideas2it.com>

* Fix autoscaler api group

Signed-off-by: Dan Sun <dsun20@bloomberg.net>
Signed-off-by: Andrews Arokiam <andrews.arokiam@ideas2it.com>

* Fix autoscaler merge

Signed-off-by: Dan Sun <dsun20@bloomberg.net>
Signed-off-by: Andrews Arokiam <andrews.arokiam@ideas2it.com>

* Fix autoscaling tests

Signed-off-by: Dan Sun <dsun20@bloomberg.net>
Signed-off-by: Andrews Arokiam <andrews.arokiam@ideas2it.com>

* Updated hpa disable test.

Signed-off-by: Andrews Arokiam <andrews.arokiam@ideas2it.com>

* Replaced "AutoscalerClassNone" with "AutoscalerClassExternal"

Signed-off-by: Andrews Arokiam <andrews.arokiam@ideas2it.com>

* Fixed autoscalerClass 'external' go test.

Signed-off-by: Andrews Arokiam <andrews.arokiam@ideas2it.com>

---------

Signed-off-by: jooho <jlee@redhat.com>
Signed-off-by: Dan Sun <dsun20@bloomberg.net>
Signed-off-by: Andrews Arokiam <andrews.arokiam@ideas2it.com>
Co-authored-by: Curtis Maddalozzo <curtis@tractable.ai>
Co-authored-by: jooho <jlee@redhat.com>
Co-authored-by: Dan Sun <dsun20@bloomberg.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants