An experiment with using their machine infrastructure instead of the ones we've
been using.
It has some drawbacks like not being able to run some of the longer time
integration tests (including fully testing the binary deploy feature) we have
in the code base. A full test and benchmark of all
Cool, I'll look into it ASAP.
What's the reason for using Travis, then? For kicks?
21.08.2017, 18:17, "John Benediktsson" :
> Yes, we have an entire continuous build system (you can look in
> `extra/mason`).
---=---
Александр
--
Yes, we have an entire continuous build system (you can look in `extra/mason`).
> On Aug 21, 2017, at 8:10 AM, Alexander Ilin wrote:
>
> What was doing the builds before Travis? Was it Factor itself? Do we have a
> Factor implementation of a build farm (like we have a web server)?
>
> I'm cu
What was doing the builds before Travis? Was it Factor itself? Do we have a Factor implementation of a build farm (like we have a web server)? I'm currently thinking about hosting a Jenking build locally for myself. Does anyone have any experience in that area? 21.08.2017, 16:44, "John Benediktsson
As far as I know, it's an issue with the win32 instance we are using in the
build farm. And it needs to be rebuilt maybe.
I wanted to ping Doug about that after solar eclipse mania settles down and see
what I can do to help also.
We started getting Travis builds working but it's not setup to
This looks perfect, thanks a lot, John! Are there any news on fixing the Windows build? What is the issue with that? Can I help? 21.08.2017, 05:13, "John Benediktsson" :I recommend reading ``basis/ui/backend/windows/windows.factor``. Particularly the ``add-wm-handler`` word. This probably requires
