Re: Design Proposal: Beam-Site Automation Reliability

2018-08-28 Thread Udi Meiri
FYI, we are about to add a new branch to apache/beam, named 'asf-site', which will contain generated website sources. On Thu, Jun 7, 2018 at 10:18 AM Jason Kuster wrote: > Sounds good; I'm really excited about these changes Scott. Thanks for > taking this on! > > On Tue, Jun 5, 2018 at 4:00 PM S

Re: Design Proposal: Beam-Site Automation Reliability

2018-06-07 Thread Jason Kuster
Sounds good; I'm really excited about these changes Scott. Thanks for taking this on! On Tue, Jun 5, 2018 at 4:00 PM Scott Wegner wrote: > Thanks everyone; I've responded to feedback in the doc [1] and I believe > we've reached consensus. I've added implementation tasks in JIRA > under BEAM-4493

Re: Design Proposal: Beam-Site Automation Reliability

2018-06-05 Thread Scott Wegner
Thanks everyone; I've responded to feedback in the doc [1] and I believe we've reached consensus. I've added implementation tasks in JIRA under BEAM-4493 [2] and will start coding soon. As a recap, the high-level plan is: * Migrate website source code to the main apache/beam repository * Discontin

Re: Design Proposal: Beam-Site Automation Reliability

2018-06-01 Thread Scott Wegner
Pre-commit filtering has come up on previous discussions as well and is an obvious improvement. I've opened BEAM-4445 [1] for this and assigned it to myself. [1] https://issues.apache.org/jira/browse/BEAM-4445 On Fri, Jun 1, 2018 at 10:01 AM Kenneth Knowles wrote: > +1 > > Can we separate preco

Re: Design Proposal: Beam-Site Automation Reliability

2018-06-01 Thread Kenneth Knowles
+1 Can we separate precommit filtering and get it set up independent from this? I think there's a lot of good directions to go once it is the norm. On Thu, May 31, 2018 at 9:25 PM Thomas Weise wrote: > Very nice, enthusiastic +1 > > On Thu, May 31, 2018 at 3:24 PM, Scott Wegner wrote: > >> Tha

Re: Design Proposal: Beam-Site Automation Reliability

2018-05-31 Thread Thomas Weise
Very nice, enthusiastic +1 On Thu, May 31, 2018 at 3:24 PM, Scott Wegner wrote: > Thanks to everyone who reviewed the doc. I put together a plan based on > the initial feedback to improve website automation reliability. At a > glance, I am proposing to: > > * Migrate website source code to the m

Re: Design Proposal: Beam-Site Automation Reliability

2018-05-31 Thread Scott Wegner
Thanks to everyone who reviewed the doc. I put together a plan based on the initial feedback to improve website automation reliability. At a glance, I am proposing to: * Migrate website source code to the main apache/beam repository * Discontinue checking-in generated HTML during the PR workflow *

Design Proposal: Beam-Site Automation Reliability

2018-05-29 Thread Scott Wegner
I've been looking into the beam-site merge automation reliability, and I'd like to get some early feedback on ideas for improvement. Please take a look at https://s.apache.org/beam-site-automation: > Apache Beam's website is maintained via the beam-site Git repository, with a set of automation tha