Build status vs. checks on jenkins.io

[Ulli Hafner]

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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1112CAB0-15E1-4110-8CBF-FCFB8B91A29C%40gmail.com.

[Xiong Kezhi]

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<[hidden email]> 写道：

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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f1550f97-1916-425c-b679-31aba59f229dn%40googlegroups.com.

[Jesse Glick-4]

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?

I think it would make sense.

If this happens, please post an announcement. At least JEP-229 would
need a minor change:
https://github.com/jglick/verify-ci-status-action/issues/1

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3_S9iu2-BSq6YvwKjWM_xegTJazVJC%3D9w_UagP68U21w%40mail.gmail.com.

[Jesse Glick-4]

I filed INFRA-2866 to track.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr116xYT3OB%2B2Bx0Ah%2Bn1K9SCqkZ4SaZhOYs-QJ_meT%3DRQ%40mail.gmail.com.

Done

On Wednesday, 6 January 2021 at 21:55:26 UTC Jesse Glick wrote:

I filed INFRA-2866 to track.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/84a0504d-74ce-43e0-b650-70d2a49e2aefn%40googlegroups.com.