On Fri, Jun 14, 2019, at 11:23 PM, Krisztián Szűcs wrote:
> On Fri, Jun 14, 2019 at 9:04 PM Wes McKinney <wesmck...@gmail.com> wrote:
>
> > hi Krisz,
> >
> > Thanks for working on this! It already helped me fix a Python 2.7-only
> > bug yesterday https://github.com/apache/arrow/pull/4553
> >
> > I have a bunch of questions:
> >
> > * What is the license of the ursabot codebase? Seems like it could be
> > GPL if Buildbot itself is [2] and you have reused any Buildbot code.
> > This is not mentioned in the README so I think you need to call this
> > out and advise people to be careful that any code contributed to this
> > codebase is stuck in GPL-land. Is it possible to separate the work
> > you've done from any GPL-ness? I don't think you can be too paranoid
> > about this kind of thing, and the longer you wait to draw a clear line
> > around any contaminated code the harder it will be to disentangle.
> >
> Created an issue for it https://github.com/ursa-labs/ursabot/issues/105
>
> >
> > * How brittle is the Buildbot master? It currently resides in my home,
> > but what if a natural disaster (like [1] from 2010) occurs in
> > Nashville causing an extended power outage (or a temporary outage
> > requiring human intervention while I'm out of town)? Is the Buildbot
> > master state backed up? Can it be easily migrated to a new host
> > (Dockerized, even)? Either way we need a contingency plan.
> >
> It doesn't have a backup yet, although it only matters for historical
> reasons.
> If I prune its database and restart the buildmaster nothing changes except
> the losing the previous builds' result - so everything will work the same
> way
> as before erasing the database.
> It can be pretty easily migrated to another host, besides setting up the
> networking with the workers and a database server (or sqlite) nothing more
> esoteric is required.
>
> >
> > * The availability of Buildbot suggests we should try to decouple our
> > CI procedures from anything Travis CI specific and use Docker instead,
> > at least for the Linux builds. This has the side benefit of enabling
> > contributors to reproduce CI build locally. Can you create some JIRAs
> > about this?
> >
> Yes, IMO docker is preferable, even for Windows containers [1]. Will do, but
> I'm curious for other's opinion too. @Uwe?
Yes, also for Windows builds docker is really nice for getting a clean
reproducible state. Only for OSX builds, you will need to boot VMs these days
when you want clean separation.
Uwe
