I did exactly as discussed with infra (commit to the buildbot config file) but nothing whatever changed. Am waiting on feedback[1] from infra as to how to tell buildbot to take notice of my commit.
Upayavira [1] https://issues.apache.org/jira/browse/INFRA-11002[1] On Tue, Dec 29, 2015, at 11:36 AM, Upayavira wrote: > I've discussed this with infra and have constructed what I believe is > a workable replacement script that will only update SVN if something > has changed. > > Unfortunately, testing it involves committing to the buildbot SVN and > waiting to see whether I've broken anything. > > I'll be doing this today, so you might see stuff go wrong. If I fail > to get my updated script to work, I'll revert to the current config. > > Upayavira > > On Sat, Dec 19, 2015, at 09:55 PM, Upayavira wrote: >> Okay. I'll dig further into how to make the commits list actually >> useful by suppressing these messages. >> >> Whilst Shawn is right - it is the human commit we are interested in - >> there's a value in having messages from Buildbot when it actually >> does something, in case someone has worked out an alternative way of >> accessing our site. >> >> I'll report back when I work something out. >> >> Upayavira >> >> On Sat, Dec 19, 2015, at 07:46 PM, Jack Krupansky wrote: >>> I had asked about these messages two and a half years ago and nobody >>> stepped forward to claim that they had any value and merely >>> suggested filtering them in the user email client. So, I'm a solid >>> +1 for suppressing them. Uwe was the only person responding to my >>> inquiry back in July 2013. >>> >>> -- Jack Krupansky >>> >>> On Sat, Dec 19, 2015 at 1:59 PM, Shawn Heisey <[email protected]> >>> wrote: >>>> On 12/18/2015 4:48 PM, Upayavira wrote: >>>> > We could prevent these messages by making the second and third steps >>>> > "dependent" upon the first. In which case, they won't occur if > no files >>>> > are changed. >>>> > >>>> > Any objections to doing this? >>>> >>>> I'm all for this change. >>>> >>>> I added a filter to my email account to move these messages into a >>>> separate folder, so that I could do "mark folder read", after >>>> looking through them for changes made by real people instead of the >>>> bot. I'm considering deleting my 2010-2014 archives for this >>>> folder, because I don't think I will ever need that information. >>>> >>>> I have a little bit of a gripe about seeing *any* notifications >>>> about buildbot updates to the website. It looks like one of the >>>> updates that happens automatically is the "Latest SVN" section on >>>> the Lucene Core page ... but I already get notified about these >>>> changes. They are the entire point of the commits mailing list. >>>> If there is any way to suppress notifications about changes to >>>> "Latest SVN", I would definitely appreciate it. >>>> >>>> We used to have a semi-live twitter feed somewhere on the website, >>>> but it looks like this no longer exists, probably since the site >>>> was redesigned. If this comes back, it is another update that I >>>> really don't need to see -- I can always subscribe via twitter if >>>> I'm interested. >>>> >>>> Thanks, Shawn >>>> >>>> >>>> ---------------------------------------------------------------- >>>> ----- >>>> To unsubscribe, e-mail: [email protected] For >>>> additional commands, e-mail: [email protected] >>>> >> > Links: 1. https://issues.apache.org/jira/browse/INFRA-11002?filter=-2
