-
Notifications
You must be signed in to change notification settings - Fork 15
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
SHIP-0023: Add SHIP for BuildRun Status Results #13
SHIP-0023: Add SHIP for BuildRun Status Results #13
Conversation
40584e3
to
7fc8db6
Compare
@imjasonh @SaschaSchwarze0 this one is ready for review, fyi |
745a240
to
cf156cf
Compare
cf156cf
to
71c88a1
Compare
71c88a1
to
f88d5ef
Compare
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.
Nice.
@qu1queee I merged your PR that brought in the old enhancement proposals. Please update the title and numbering to SHIP-0022 so we don't have collisions. Thanks! |
I´m closing this one as I cannot provide updates here for the next upcoming weeks. @SaschaSchwarze0 you might wanna re-open with a cherry-pick and changes on top. @HeavyWombat fyi. |
c698bab
to
a1a237c
Compare
a1a237c
to
ad61f70
Compare
This SHIP provides a proposal on how to surface Tekton Task Results into the BuildRun Status subresource.
Co-authored-by: Sascha Schwarze <[email protected]>
ad61f70
to
20653f2
Compare
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.
Just some small things. I cannot (yet) approve in this repo. Proposed it here.
} | ||
|
||
type Output struct { | ||
DigestOutputResult string `json:"digest,omitempty"` |
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.
To conform with our rule that the Go field should be called just like the JSON property.
DigestOutputResult string `json:"digest,omitempty"` | |
Digest string `json:"digest,omitempty"` |
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.
Agree that we should adhere to this in the implementation, I don't think we should block merge of the proposal.
|
||
type GitSourceResult struct{ | ||
CommitSha string `json:"commit-sha,omitempty"` | ||
CommitAuthor string `json:"commit-author,omitempty"` |
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.
CommitAuthor string `json:"commit-author,omitempty"` | |
CommitAuthor string `json:"commit-author,omitempty"` // Not existing today, but outlining how it would look with multiple results |
} | ||
|
||
type HttpSourceResult struct{ | ||
Size int `json:"size"` |
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.
Size int `json:"size"` | |
Size int `json:"size"` // Not existing today, but outlining how it could look for HTTP |
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.
/approve
} | ||
|
||
type Output struct { | ||
DigestOutputResult string `json:"digest,omitempty"` |
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.
Agree that we should adhere to this in the implementation, I don't think we should block merge of the proposal.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adambkaplan 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 |
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
This SHIP provides a proposal on how to surface Tekton Task Results into the BuildRun Status subresource.
It proposes three types of new fields under the .status subresource, these being:
.status.results
.status.sources
.status.output