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

Use newly added name field in step status to find correct results #95

Merged
merged 1 commit into from
Apr 26, 2019

Conversation

AlanGreene
Copy link
Member

#56

Instead of attempting to match step status in task runs by index,
accounting for presence / order of init containers, use the
newly added name field in the step status so we can reliably
link steps to their status and logs regardless of order.

This involves updating Gopkg.lock to use github.com/tektoncd/pipeline
revision 3415c18f7728476c132f692d9a55a70b7b194c5d which introduced
the new field.

Instead of attempting to match step status in task runs by index,
accounting for presence / order of init containers, use the
newly added name field in the step status so we can reliably
link steps to their status and logs regardless of order.

This involves updating Gopkg.lock to use github.com/tektoncd/pipeline
revision 3415c18f7728476c132f692d9a55a70b7b194c5d which introduced
the new field.
@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 26, 2019
@AlanGreene
Copy link
Member Author

/hold
@a-roberts this is the change we discussed earlier in the week. There's no reliable way to identify the correct step status without the new field. If you have no objections to updating the version of pipeline we consume this should be good to go.

@tekton-robot tekton-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 26, 2019
@AlanGreene
Copy link
Member Author

/assign @a-roberts

Copy link
Member

@steveodonovan steveodonovan left a comment

Choose a reason for hiding this comment

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

Approved. Someone from marks team also needs to review

@a-roberts
Copy link
Member

So we're not breaking anything on 0.2 and we're benefitting from a new change that went into master about a week ago and thus the 0.3 release right @AlanGreene?

@AlanGreene
Copy link
Member Author

That's right, everything else appears to be working as expected.

@a-roberts
Copy link
Member

Sounds good to me then, thanks

/approve
/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 26, 2019
@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: a-roberts, AlanGreene, steveodonovan

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:
  • OWNERS [AlanGreene,a-roberts]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@AlanGreene
Copy link
Member Author

/hold cancel

@tekton-robot tekton-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 26, 2019
@tekton-robot tekton-robot merged commit 170fa38 into tektoncd:master Apr 26, 2019
@AlanGreene AlanGreene deleted the step_status branch April 26, 2019 16:01
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. 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.

4 participants