Hi, well … I would like to bring the idea of making the build more solid, that there are less failures? It did seem as if there are some flaky tests. Not quite sure, but I think having build failures on “develop” on the list is good. Build failures of non-develop branches however not.
We’re currently working hard in PLC4X in fixing issues failing the build regularly/randomly. If we move them somewhere else, we’re running danger to simply no longer pay attention to the build failing. Chris Von: Jialin Qiao <[email protected]> Datum: Freitag, 30. Juni 2023 um 11:33 An: [email protected] <[email protected]> Betreff: Re: [discuss] move jenkins build message to a new mailing list +1 for option 1 Thanks, ――――――――――――――――― Jialin Qiao Apache IoTDB PMC Haonan Hou <[email protected]> 于2023年6月30日周五 17:31写道： > > +1 for option 1. > > Best, > Haonan Hou > > > On Jun 29, 2023, at 11:44 PM, Xiangdong Huang <[email protected]> wrote: > > > > Hi all, > > > > How do you think about move jenkins's notification > > "build-failure"/"build-stable" to a new mailing list? > > > > Now, it is sent to dev@, and some people may think it is annoying.. > > > > So, how do you think about it? > > > > option 1: move to an existed mailing list: notifications@ (which is > > for jira issues now) > > option 2: create a new mailing list. > > option 3: keep current status > > > > Best, > > ----------------------------------- > > Xiangdong Huang >
