-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Display last updated time for Tasks, Pipelines, Resources #733
Comments
/assign @nikhil-thomas |
@nikhil-thomas: GitHub didn't allow me to assign the following users: nikhil-thomas. Note that only tektoncd members and repo collaborators can be assigned. 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. |
@nikhil-thomas let me know if you want to be added to the |
@bobcatfish Thank you for adding me 👍 |
/assign @nikhil-thomas |
/assign |
@piyush-garg are you still working on this? |
@bobcatfish Yaa, I am working on this. Sorry for the delay. @imjasonh The solution you suggested is to use Conditions. But I see the status for Pipeline or Task is deprecated. Should I use Conditions in Spec? or I remove the deprecation? or any other suggestions? There is this issue kubernetes/kubernetes#12430 for adding the field in ObjectMeta |
ah good point, we remove those Status field because they weren't used at all 🤔 |
Can this be worked on? I'm looking for a first issue to take on. |
Of course 😉 You can do /assign @AhmaudArbery |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. 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. |
/remove-lifecycle rotten |
@vdemeester: Reopened this issue. 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. |
@AhmaudArbery and @JoaoVitoGomesa are you still working on this one? |
No feel free to remove me
…On Tue, Sep 1, 2020, 3:18 PM Christie Wilson ***@***.***> wrote:
@AhmaudArbery and @JoaoVitoGomesa are you still working on this one?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#733 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA2GCMS2YDOH7PFVBX4TUUTSDVJKTANCNFSM4HD4AXIA>
.
|
@bobcatfish I would like to work on this. I will need some time to look at the possible solutions now. Or do you have something in mind that can be done for this? Outcomes from my previous try #733 (comment) |
@bobcatfish @vdemeester @imjasonh The last updation time can be retrieved from |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. 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. |
Expected Behavior
After updating a Task, Pipeline or Resource definition,
kubectl get pipeline my-pipeline
should give some indication of when it was last updated.Actual Behavior
Instead, it only displays the resource's age (time since creation), which is somewhat less helpful.
Steps to Reproduce the Problem
kubectl get
itAdditional Info
TaskRuns and PipelineRuns have a
lastTransitionTime
in its.Status.Conditions
, which is configured to be displayed inkubectl
output.It probably makes sense for Pipelines, etc., to define Conditions too, which will give it a
lastTransitionTime
which I believe will be automatically updated by knative/pkg internals, and which might be useful in the future.This also enables users to list resources sorted by last update time, or to only show recently-updated resources, etc.
cc @skim1420
The text was updated successfully, but these errors were encountered: