I think we're already using this method to deploy the site?: https://ci.apache.org/builders/asterixdb-master-docs . It just builds from the asf-site branch every night. I suppose it is not as good as the build being triggered by a push but it generally suffices.
The issue most of the time so far has been that, we don't have a way to modify the builder settings. So whenever something changes in the source that doesn't play well with how it is configured, it will break, and we have to ask infra to fix it for us, even though I think in most cases it is simple things that cause it (path changes, etc). Is there a way for the team to have access to change the configs whenever something breaks? -Ian On Sun, Jul 10, 2016 at 11:06 PM, Till Westmann <[email protected]> wrote: > Hi Jochen, > > I’m not too familiar with buildbot, but this sounds really interesting. > > So it seems that there’s a way not to submit to an Apache git repo without > a > human in the loop. > Is that right? > If so, is that only true for the site or would that also be true for the > code repository? > Also, would such a submission retain identifying information about the > original committer? > > Ok, these are a number of questions about buildbot, and you're probably not > the right person to answer them. But, if you know some of the answers or > have pointers to how things work, please share them. > > Thanks! > Till > > > On 10 Jul 2016, at 3:29, Jochen Wiedmann wrote: > > Hi, >> >> may I raise your attention to a comment made by David Gruno on >> INFRA-12228: >> >> because you want something to build your web site for you? >> >> This is possible with buildbot now (we have a git role account), >> please make a separate ticket >> for that. >> >> Jochen >> >> -- >> The next time you hear: "Don't reinvent the wheel!" >> >> >> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg >> >
