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). 在2020年11月23日星期一 UTC+8 下午4:56:04<[email protected]> 写道：
> 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 I get two different results from Jenkins (and the old one is > wrong since it assumes that status UNSTABLE means that there are test > failures): > > 1) Jenkins > 2) continuous-integration/jenkins/pr-merge — This commit has test failures > > > > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f1550f97-1916-425c-b679-31aba59f229dn%40googlegroups.com.
