I'm not sure if this is a situation we need to take care of:
The branch source plugin may publish two builds including the merge build and branch build (if a pr is opened long after the branch is pushed?) to the PR, but the github-checks will publish only one since we used the build listener (the one for the branch will be replaced later if you file a PR based on that branch).
On Mon, Nov 23, 2020 at 3:56 AM Ullrich Hafner <[hidden email]> wrote:
> Since we have successfully integrated the GitHub checks in buildPlugin for quite a while: would it make sense to disable the old build status results on https://ci.jenkins.io?
Currently a successful incremental deployment is shown with a separate GitHub checks output, this is very handy to directly jump to the new release. Would it make sense to add a negative (or neutral) check in case something went wrong? E.g., if the PR is not in sync with the base branch then the check result is completely missing. In such a case one needs to dig into the console log just to see that the branch is not in sync.