-
Notifications
You must be signed in to change notification settings - Fork 356
Send build completion notification for pull requests merged after build start #472
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
Open
mguillem
wants to merge
13
commits into
jenkinsci:master
Choose a base branch
from
mguillem:feature/push-notification-for-merged-pull-request
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
a88d25f
find SCMSource even if NullSCM now associated to build
mguillem 1efe285
Merge branch 'master' into feature/push-notification-for-merged-pull-…
mguillem 78188ba
Merge branch 'master' into feature/push-notification-for-merged-pull-…
mguillem da983b7
Merge branch 'master' into feature/push-notification-for-merged-pull-…
lifeofguenter 9381971
Merge branch 'master' into feature/push-notification-for-merged-pull-…
mguillem ce2cdcd
Merge branch 'master' into feature/push-notification-for-merged-pull-…
lifeofguenter 515413b
Merge branch 'master' into feature/push-notification-for-merged-pull-…
mguillem 60d1ca7
Merge branch 'master' into feature/push-notification-for-merged-pull-…
mguillem e351ac0
Merge branch 'master' into feature/push-notification-for-merged-pull-…
lifeofguenter de063c2
Merge remote-tracking branch 'upstream/master' into
mguillem 00ccdd6
Merge branch 'master' into feature/push-notification-for-merged-pull-…
lifeofguenter 9a49a14
Merge branch 'master' into feature/push-notification-for-merged-pull-…
lifeofguenter 3475390
Merge branch 'master' into feature/push-notification-for-merged-pull-…
lifeofguenter File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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 a Jenkins multibranch job has multiple SCM sources (e.g. an original repository and a fork with distinct branch names), I think this might not select the correct one.
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.
On the other hand, because this plugin is using the older REST API that does not distinguish between repositories, it will work anyway, as long as the repositories are on the same server.
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.
But a similar fix might not be valid for jenkinsci/github-checks-plugin#196 because the GitHub API Create a check run is at POST /repos/{owner}/{repo}/check-runs and presumably has to be told the correct 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.
This fix worked for me and was quite easy to implement. A solution to be really safe would be probably to save the url to which the INPROGRESS event has been sent to reuse it at build completion.
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.
Not only the URL but also the credential ID.
I think this change is fine for bitbucket-branch-source-plugin, but we need something more reliable for the equivalent issue in github-checks-plugin and in the future bitbucket-server-checks-plugin.
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 someone say whether the proposed fix can be merged (and do it) or otherwise provide feedback about what should be changed? Thanks.