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
ODC-7384: Update the PipelineRun details page to use Tekton Results API to load all the info #13313
Conversation
@lokanandaprabhu: This pull request references ODC-7384 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.0" version, but no target version was set. In 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: lokanandaprabhu The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
bb8a1a1
to
d374a91
Compare
d374a91
to
3c42594
Compare
/uncc christianvogt rottencandy |
3c42594
to
f1c6374
Compare
f1c6374
to
5be0c36
Compare
5be0c36
to
ce7c31c
Compare
Hi @vikram-raj / @jerolimov I updated the PR. PTAL. Thanks. |
ce7c31c
to
dd015e3
Compare
dd015e3
to
5e5688a
Compare
@lokanandaprabhu: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
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.
internet.network.call.on.PLR.details.page.mov
I noticed an issue. On the details page, there is a continuous network call for results API.
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.
const [pipelineRun, pipelineRunLoaded] = useK8sWatchResource<FirehoseResult<K8sResourceKind>>({ | ||
kind: referenceForModel(PipelineRunModel), | ||
namespace, | ||
name, | ||
isList: false, | ||
}); | ||
const [TRPlrs, TRPlrsLoaded] = useTRPipelineRuns(namespace, { | ||
selector: { filterByName: name }, | ||
}); | ||
|
||
React.useEffect(() => { | ||
setData(pipelineRun || TRPlrs[0]); | ||
setLoaded(pipelineRunLoaded || TRPlrsLoaded); | ||
}, [TRPlrs, pipelineRun, pipelineRunLoaded, TRPlrsLoaded]); |
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.
You can extract this logic as a separate hook called usePipelineRun
, so that this hook can be used elsewhere in the codebase as well.
obj={{ | ||
data, | ||
loaded, | ||
loadError: undefined, |
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.
Shouldn't we pass the actual error object here?
In pipelinerun details page, we will be fetching all the taskruns as well. So when you delete a pipelienrun (which will inturn delete all the taskruns automatically from K8s cluster) and then go to that deleted details page you can see the visualization with wrong task status, we need to use tekton-results for fetching the taskruns here as well. |
Closing this PR since it is handled in PR - #13328 /close |
@lokanandaprabhu: Closed this PR. In 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. |
Story : https://issues.redhat.com/browse/ODC-7384