Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[JENKINS-46795]
TrustworthyBuild
extension point #180base: master
Are you sure you want to change the base?
[JENKINS-46795]
TrustworthyBuild
extension point #180Changes from 4 commits
23aadee
4d9ad1a
6e7c68f
ebe3d6f
57bfecc
7e98857
013950c
e5707b7
7ea44f8
f6ec0d0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
While it should be rare, there can be multiple causes of the same type for a build that aren't collapsed into one entry. Whether a build is approved or not could depend on the (insertion) order of the
CauseAction#causeBag
.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.
The API does not prevent it but this ought never happen—it is the responsible of code triggering the build to pass at most one
Cause
of any given type. At worst a build is not considered trusted when it could have been, so this does not seem like a problem in practice.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.
Could pass
true
but we expect theUser
to have just been loaded anyway.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.
Could be defined more modularly as an extension in
workflow-cps
, but would be awkward since the rest of this impl would need to be duplicated, andordinal
used to avoid printing misleading messages.In practice the callers of
getTrustedRevisionForBuild
are going to be in Pipeline code so I am not too concerned.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.
jenkinsci/github-checks-plugin#307