What are we going to do about mobile?

[Iain Buclaw via Digitalmars-d]

On 16 April 2017 at 09:41, Johannes Pfau via Digitalmars-d
<digitalmars-d at puremagic.com> wrote:
> Am Sat, 15 Apr 2017 15:11:08 +0000
> schrieb Laeeth Isharc <laeethnospam at nospam.laeeth.com>:
>> Gitlab has test runners built in, at least for enterprise version
>> (which is not particularly expensive) and we have been happy with
>> that.
>>
>> Laeeth
>>
>
> The free version has test runner as well. What bothers me about gitlab
> is the github integration. gitlab-CI only works with a gitlab instance
> so you have to mirror the github repository to gitlab. This is usually
> not too difficult, but you have to be careful to make pull request
> tsting and similar more complex ffeatures work correctly. I also think
> they don't have anything ready to push CI status to github.
>
>
> -- Johannes
>

I asked at a recent D meetup about what gitlab CI used as their
backing platform, and it seems like it's a front for TravisCI.  YMMV,
but I found the Travis platform to be too slow (it was struggling to
even build GDC in under 40 minutes), and too limiting to be used as a
CI for large projects.

Whereas I don't really have much bad to say about Semaphore, as it's
able to download, build, *and* run testsuite in under 15 minutes at
the best of times [1].

Johannes, what if I get a couple new small boxes, one ARM, one
non-descriptive x86.  The project site and binary downloads could then
be used to the non-descriptive box, meanwhile the ARM box and the
existing server can be turned into a build servers - there's enough
disk space and memory on the current server to have a at least half a
dozen build environments on the current server, testing also i386 and
x32 would be beneficial along with any number cross-compilers
(testsuite can be ran with runnable tests disabled).

[1]: https://semaphoreci.com/d-programming-gdc/gdc/branches/master/builds/330