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

Show pipeline details embedded in runs #447

Merged
merged 8 commits into from
Dec 4, 2018

Conversation

yebrahim
Copy link
Contributor

@yebrahim yebrahim commented Dec 3, 2018

Runs created in notebooks (or created the same way using API/CLI) do not contain a pipeline ID reference. Instead, they contain the entire pipeline spec embedded inside the run object. This PR handles extracting the pipeline details from there and showing them in the PipelineDetails view.

Some other small fixes:

  • Moved QUERY_PARAMS to Router component to make all routing definitions in one place.
  • Changed pipeline id to be an optional parameter for the PipelineDetails page.
  • Changed the custom renderer methods on RunList to be public. I think this makes more sense, since they really are part of the public API, and can be called as such.

Part of #75.


This change is Reviewable

frontend/src/components/Router.tsx Show resolved Hide resolved
frontend/src/components/Router.tsx Show resolved Hide resolved
frontend/src/lib/RunUtils.ts Outdated Show resolved Hide resolved
frontend/src/pages/PipelineDetails.test.tsx Show resolved Hide resolved
frontend/src/pages/PipelineDetails.tsx Show resolved Hide resolved
frontend/src/pages/PipelineDetails.tsx Show resolved Hide resolved
frontend/src/pages/PipelineDetails.tsx Outdated Show resolved Hide resolved
return (
<Link className={commonCss.link} onClick={(e) => e.stopPropagation()}
to={url}>
{pipelineInfo.showLink ? 'View pipeline' : pipelineInfo.displayName}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I think maybe [View pipeline] would be better? something to help distinguish it visually from a normal pipeline name?

Or maybe we don't actually care about that

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should distinguish them too. I'll add @ajayalfred here for follow up, but for now I think we can merge this whenever it's ready until we hear back from him.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll check with Jordan and comment back here.

@yebrahim
Copy link
Contributor Author

yebrahim commented Dec 4, 2018

/test build-image

@rileyjbauer
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rileyjbauer

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

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rileyjbauer

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

@k8s-ci-robot k8s-ci-robot merged commit 9718826 into master Dec 4, 2018
@yebrahim yebrahim deleted the yebrahim/run-pipeline-spec branch December 4, 2018 19:18
Linchin pushed a commit to Linchin/pipelines that referenced this pull request Apr 11, 2023
* kind/feature should also use improvement/enhancement as previous value
* Cleanup some of the area labels

Related to kubeflow#440
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.

4 participants