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.
> Am 23.11.2020 um 15:59 schrieb Jesse Glick <[email protected]>: > > On Mon, Nov 23, 2020 at 3:56 AM Ullrich Hafner <[email protected]> > 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 [email protected]. > 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. -- 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/B45C82E8-B963-4696-B822-19B36606B64C%40gmail.com.
