-
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
Add Build status fields to TaskRun status #243
Add Build status fields to TaskRun status #243
Conversation
/test pull-knative-build-pipeline-integration-tests |
e93fa49
to
1d97125
Compare
4ef652c
to
69a62e0
Compare
# […]
I1120 15:23:03.717] status:
I1120 15:23:03.717] conditions:
I1120 15:23:03.718] - lastTransitionTime: "2018-11-20T15:16:50Z"
I1120 15:23:03.718] message: All Tasks have completed executing
I1120 15:23:03.718] reason: Succeeded
I1120 15:23:03.718] status: "True"
I1120 15:23:03.718] type: Succeeded
# […]
I1120 15:23:03.758] --- FAIL: TestHelmDeployPipelineRun (329.85s)
I1120 15:23:03.758] helm_task_test.go:177: Image to be pusblished: gcr.io/knative-boskos-09/kbuild-pipeline-e2e-img/go-helloworld-image-sueovuam
I1120 15:23:03.758] helm_task_test.go:141: Error from pinging service IP 35.239.144.181 : timed out waiting for the condition Looking at that error (and the object above that log), it feels like it's flakey 🤔 /test pull-knative-build-pipeline-integration-tests |
@@ -68,8 +68,7 @@ type TaskSpec struct { | |||
|
|||
// TaskStatus defines the observed state of Task | |||
type TaskStatus struct { | |||
// INSERT ADDITIONAL STATUS FIELD - define observed state of cluster | |||
// Important: Run "make" to regenerate code after modifying this file | |||
// Important: Run "./hack/update-codegen.sh" to regenerate code after modifying this file |
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.
🙏 thank you!
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.
p.s. really appreciate your attention to detail cleaning up lots of comments and docs @vdemeester !!! ❤️
state := build.Status.StepStates[i] | ||
tr.Status.Steps = append(tr.Status.Steps, v1alpha1.StepState{ | ||
ContainerState: *state.DeepCopy(), | ||
// FIXME(vdemeester) logsURL |
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.
if this is something you intend to fix in a further PR can you add a bit more detail about what needs to happen here?
if you plan to fix it in this PR just ignore me :D
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.
Ah right, I should add more context to this… So there is a LogsURL
field in the StepState
(previously StepRun
), which was not populate (and still is not). That's why the FIXME here, to not forget… but really, to not forget we shoul create an issue, not a comment 😝
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 have strong feelings about moving the test logic down a level, into a unit test and out of the reconciler test.
Thanks so much for taking this on!!
Yes, definitely agree on that 🙌 This needs refactoring, and I'll do the refactoring in the PR very shortly 😉 |
69a62e0
to
74ca9f7
Compare
/test pull-knative-build-pipeline-integration-tests |
everything looking good @vdemeester but I don't know why the helm test in so flakey for you, I didn't have any trouble with it before /test pull-knative-build-pipeline-integration-tests |
I think there is currently some issue with gcr.io (at least I have some from my network) |
/test pull-knative-build-pipeline-integration-tests |
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.
All the comments so far have been addressed. Thanks @vdemeester
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pivotal-nader-ziada, 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 |
@vdemeester looks like you might have to rebase |
@pivotal-nader-ziada oh boy 😅 Will do :) |
Updates TaskRunStatus to have the BuildStatus fields (non-deprecated ones) and populate them from the scheduled build status. Signed-off-by: Vincent Demeester <[email protected]>
Extract updating the TaskRunStatus from reconcile so we can test it in isolation. Signed-off-by: Vincent Demeester <[email protected]>
Signed-off-by: Vincent Demeester <[email protected]>
74ca9f7
to
968036c
Compare
The following is the coverage report on pkg/.
|
Thanks @vdemeester /lgtm |
Updates TaskRunStatus to have the BuildStatus fields (non-deprecated ones) and populate them from the scheduled build status.
Simple naive approach.
, puttingWIP
as I need to add/update tests (unit tests 😉).Closes #236
/cc @pivotal-nader-ziada @imjasonh @bobcatfish
Signed-off-by: Vincent Demeester [email protected]