-
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
Changes to add results to a task #1888
Conversation
The following is the coverage report on pkg/.
|
8272710
to
2ee1b46
Compare
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
24ef369
to
2f81a4b
Compare
The following is the coverage report on pkg/.
|
2f81a4b
to
d8a0190
Compare
The following is the coverage report on pkg/.
|
pkg/entrypoint/entrypointer.go
Outdated
output = append(output, v1alpha1.PipelineResourceResult{ | ||
Key: resultFile, | ||
Value: string(fileContents), | ||
ResultType: "result", |
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.
Can we use the new ResultType
here instead of hard coding this string?
docs/developers/README.md
Outdated
@@ -185,7 +185,7 @@ There are known issues with the existing implementation of sidecars: | |||
|
|||
- When the `nop` image does provide the sidecar's command, the sidecar will continue to | |||
run even after `nop` has been swapped into the sidecar container's image | |||
field. See https://github.com/tektoncd/pipeline/issues/1347 for the issue | |||
field. See <https://github.com/tektoncd/pipeline/issues/1347> for the issue |
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.
Minor nit: since we're changing this file, I suggest updating it to See [the issue tracking this bug](https://github.com/tektoncd/pipeline/issues/1347)
.
// Name the given name | ||
Name string `json:"name"` | ||
|
||
// Description the given description |
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.
Suggest tweaking the wording and adding an +optional tag so it becomes:
// Description is a human-readable description of the result
// +optional
d5a867a
to
2351005
Compare
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
8b35cdf
to
fe71c51
Compare
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
/test pull-tekton-pipeline-integration-tests |
yikes! twice in a row 🤔 |
The following is the coverage report on pkg/.
|
@vdemeester What kind of doc update do you want? |
@@ -51,6 +52,12 @@ func main() { | |||
Waiter: &realWaiter{}, | |||
Runner: &realRunner{}, | |||
PostWriter: &realPostWriter{}, | |||
Results: strings.Split(*results, ","), | |||
} | |||
if len(e.Results) >= 1 && e.Results[0] != "" { |
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.
I am curious - what is the purpose of the e.Results[0] != ""
check?
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.
This is because strings.Split("", ",") returns an array with an empty string in it. So an empty string means we try to read the folder as a file and it fails.
Since this change is mostly internal to Tekton (for now... it will be exposed to users in an upcoming PR based on this work) I think the best place for documentation would be in Does that make sense? |
d66bb0d
to
402cbd7
Compare
@sbwsg should the doc update be part of this PR? |
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
@othomann yeah I think so. |
7429052
to
8ebcada
Compare
8ebcada
to
b7996ee
Compare
/approve |
@sbwsg ok done. Commits squashed and tests are running again. Let me know if there is anything else that is needed to get this approved. |
The following is the coverage report on pkg/.
|
The following is the coverage report on pkg/.
|
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
/meow
I'll update v1alpha2 struct accordingly 👼
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 APPROVED This pull-request has been approved by: sbwsg, 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 |
Interesting, the rebase made the lint fail 😅 |
/test pull-tekton-pipeline-build-tests |
@vdemeester I haven't changed the files |
@othomann it was some previous PR merged that did that, it got fixed 😉 |
Changes
This is the first set of changes that modifies the task spec to add results. It also modifies the entrypoint to feed the termination log with the expected results.
It also adds a new cli argument to the entrypoint cmd (-results).
Part of #1273
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.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes