Thanks for the explanation, Kenn, I appreciate. Indeed my commits were on the website, so probably that's it.
I presume not, but can I do something to facilitate the process? Best, Stefano Sent from Blue On Jun 27, 2018, 17:23, at 17:23, Kenneth Knowles <[email protected]> wrote: >First let me say what I think the cause is: > > - we have most jobs set to "email people who broke the build" >- this scrapes what Jenkins thinks all the changes since last time are, >and for every registered address, sends email > - when we create a new job with these settings, *all* changes are >considered new, and jobs usually start broken, so everyone gets email >until >the first passing run >- also we bulk merged the web site into the main repo, so *all* website >commits were also considered for all existing jobs > >We have had some other issues where Jenkins is emailing people with >*no* >commits at all in any repo. Presumably due to an issue with looking up >registered users. > >I think we should just turn off "email people who broke the build". We >have >other channels to monitor the status, and we don't need this spam or >administrative work. > >Kenn > >On Wed, Jun 27, 2018 at 8:10 AM <[email protected]> wrote: > >> Hi all, >> >> I've contributed a couple of lines of code a couple of years back. >Ever >> since a week, I started receiving email notification from Jenkins. >> >> How do I unsubscribe from those? I don't have an account on >> builds.apache.org. >> >> Best, >> Stefano >>
