So the code that controls when which email is sent where is here: https://github.com/apache/iotdb/blob/master/Jenkinsfile#L185
I am not sure Jenkins can be configured to send emails to the authors of breaking builds. I think that’s a goodie only GitHub Actions have. Chris PS: It seems you are posting from an email address that is not subscribed. I had to moderate all of your emails today … Von: 谭新宇 <[email protected]> Datum: Freitag, 15. März 2024 um 16:16 An: [email protected] <[email protected]> Betreff: Re: Keeping an eye on Jenkins Hi, Chris Late last year, we spent several months fixing the unstable UT/IT to get Github CI and Jenkins CI up and running. After our efforts, both of them should be stable for several weeks. However, the last few months have brought some new CI instability issues, this time a rat file, and so on. To produce snapshot builds successful and take CI stability into account, perhaps we can configure Jenkins CI to route successful builds to a trash list and otherwise alert the developer of failed builds. For example, send to dev list or a feishu group. Best ————————— Xinyu Tan > 2024年3月13日 22:52，Christofer Dutz <[email protected]> 写道： > > Hi all, > > So, I just had a look at our Jenkins build as in the past we had several > occasions where we were having failing builds for many days. > Turns out for the last 4 days Jenkins has been continuously failing because > of a trivial RAT violation. > > However, have we not been producing SNAPSHOT versions, and nobody noticed, > because we decided to redirect build failure emails of Jenkins to a > trash-list. > > We really should discuss how to deal with failing builds. > > I personally think redirecting failed build notifications is the worst way to > deal with a flaky build. > Instead, we really should work on ironing out the issues that are randomly > failing. > > Having a stable and solid build should be of upmost importance, as only with > this can we truly trust the CI. > > > Chris
