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

Set TaskRun Completion time in case of Failure or Success 🏁 #740

Merged
merged 1 commit into from
Apr 8, 2019

Conversation

vdemeester
Copy link
Member

Changes

Before this change, the completion time of a TaskRun is only set in
case of a timeout, which is not quite right.

While reviewing #718, I discovered that we only update the CompletionTime of a TaskRun in case of a Timeout.

cc @abayer

Signed-off-by: Vincent Demeester vdemeest@redhat.com

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide
for more details.

Release Notes

Fix CompletionTime missing in TaskRun status

Before this change, the completion time of a TaskRun is only set in
case of a timeout, which is not quite right.

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@googlebot googlebot added the cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit label Apr 8, 2019
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

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

@tekton-robot tekton-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Apr 8, 2019
@chmouel
Copy link
Member

chmouel commented Apr 8, 2019

/lgtm

@tekton-robot
Copy link
Collaborator

@chmouel: changing LGTM is restricted to assignees, and only tektoncd/pipeline repo collaborators may be assigned issues.

In response to this:

/lgtm

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.

@vdemeester
Copy link
Member Author

/test pull-tekton-pipeline-integration-tests

@abayer
Copy link
Contributor

abayer commented Apr 8, 2019

/lgtm

Oops. =)

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 8, 2019
@tekton-robot tekton-robot merged commit 395bc32 into tektoncd:master Apr 8, 2019
@vdemeester vdemeester deleted the taskrun-completion-time branch April 8, 2019 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants