[Testing] Using Travis CI (or better alternative) for master/branch/PR testing

[Iain Buclaw via D.gnu]

On 23 June 2015 at 20:05, Marko Anastasov via D.gnu <d.gnu at puremagic.com>
wrote:

> On Tuesday, 23 June 2015 at 17:48:23 UTC, Iain Buclaw wrote:
>
>>
>> So it is possible to manage the `.semaphore-cache` directory in a
>> scriptable way then?  I'm thinking in terms of checking whether a tarball
>> exists either downloading or extracting based on the outcome.
>>
>
> Yes, the directory is always present and you can write a script based on
> the presence or absence of its content. Note that Semaphore build commands
> can be Bash commands too. Some people tend to encapsulate things in a .sh
> file as things get more complex.
>
>
>> I see that is an `Expire Dependency Cache` button for the build, I assume
>> this cleans up the `.semaphore-cache` directory for us.
>>
>
> Yes.
>
>
>
OK, Thanks.  I've added in some logic using the exposed `BRANCH_NAME`
environment variable, and now saving tarballs to cache.  Just triggered a
build for gcc-5, gcc-4.9, and gcc-4.8 on my own repository.  I'll
re-trigger one last build for master to verify that the tarballs are kept
locally between builds, then I'll promise I'll stop "hammering" your build
servers. :-)

@Johannes, I've created a GDC team on semaphoreci, will add you to it along
with the build configuration I've set-up so far.  I imagine this will be
rolled out tomorrow.  Let's see how this goes...

Iain.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/d.gnu/attachments/20150623/de30bf02/attachment.html>