-
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
implementing TEP-0150 - displayName
in childReferences
#7683
implementing TEP-0150 - displayName
in childReferences
#7683
Conversation
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
bb37fc9
to
b84b8a2
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
b84b8a2
to
c6a0bed
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
c6a0bed
to
d5256ea
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/test pull-tekton-pipeline-integration-tests |
Thanks @afrittoli! That is correct. The |
Thanks @pritidesai. I think concatenation makes sense. As I mentioned, I find the current matrix API a bit hard to parse, but that's not something for this to address. Given the current matrix API, the proposed display name makes sense. Perhaps we should have one case in the test list where display name remains empty to check that case too? |
d5256ea
to
4fbb1e5
Compare
We have a variety of tests written under pipelinerunstate_test.go which include the case where the displayName remains empty when include params does not make it as part of the combinations: Let me know if we want to add more tests. Thanks! |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/retest Hey @AlanGreene @AverageMarcus, this is ready for review, PTAL! Thanks! |
/retest |
1 similar comment
/retest |
Pipeline WG: @AlanGreene @AverageMarcus PTAL again since we are hoping to get this merged this month. |
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.
/lgtm
@AverageMarcus: changing LGTM is restricted to collaborators 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. |
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.
Pipeline WG: @AlanGreene @AverageMarcus PTAL again since we are hoping to get this merged this month.
The latest updates to the docs and examples look good based on our discussions and previous feedback, and as far as I can tell the test updates make sense too.
However, I'm not familiar enough with the codebase to determine whether the implementation has any potential impact on other features / functionality, in particular the changes in ApplyReplacements
. A Pipelines maintainer or contributor would need to review and comment on that.
4fbb1e5
to
39daaf7
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
@tektoncd/core-maintainers please help review this PR. Thanks in advance! |
This is a very simple change in adding human readable name in the childReferences. As an end user, we are waiting for this feature. Will appreciate if we can get the community to review on this PR. Thanks in advance! |
Implementing proposal TEP-0150. Adding a functionality where the existing displayName can be used to configure unique names for each instance using the params from each combination such that the matrix instances in the Tekton Dashboard are rendered to distinguishable names. Also, repurposing an existing name field as part of the matrix.include[].name. If specified, a fully resolved name field is available in the childReferences. Signed-off-by: Priti Desai <pdesai@us.ibm.com>
39daaf7
to
a9f4b61
Compare
The following is the coverage report on the affected files.
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chitrangpatel 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 |
The following is the coverage report on the affected files.
|
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.
Thanks @pritidesai for the extra test and updates.
I only left a NIT comment, but nothing blocking really - maybe something for another PR.
/lgtm
TypeMeta: runtime.TypeMeta{ | ||
APIVersion: "tekton.dev/v1", | ||
Kind: "TaskRun", | ||
}, | ||
Name: "matrixed-task-run-2", | ||
PipelineTaskName: "matrixed-task", |
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.
+1
@@ -240,8 +242,53 @@ func (facts *PipelineRunFacts) GetChildReferences() []v1.ChildStatusReference { | |||
return childRefs | |||
} | |||
|
|||
func (t *ResolvedPipelineTask) getDisplayName(customRun *v1beta1.CustomRun, taskRun *v1.TaskRun, c v1.ChildStatusReference) v1.ChildStatusReference { |
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.
NIT: I find the name/structure of this function slightly confusing - it does not return the display name, instead it sets it on a ChildStatusReference
that must be passed as input.
Since the ChildStatusReference
is not used to build the displayName, I thought it would be better to have a getDisplayName
function that returns a string - any particular reason for having it this way?
Changes
Implementing proposal TEP-0150.
Adding a functionality where the existing displayName can be used to configure unique names for each instance using the params from each combination such that the matrix instances in the Tekton Dashboard are rendered to distinguishable names.
Also, repurposing an existing name field as part of the matrix.include[].name. If specified, a fully resolved name field is available in the childReferences.
Fixes #7082
/kind feature
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes