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

2015-06-23 Thread Marko Anastasov via D.gnu
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

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

2015-06-23 Thread Marko Anastasov via D.gnu
On Tuesday, 23 June 2015 at 14:57:55 UTC, Iain Buclaw wrote: On 23 June 2015 at 12:31, Iain Buclaw wrote: On 23 June 2015 at 10:15, Marko Anastasov via D.gnu wrote: On Monday, 22 June 2015 at 08:56:54 UTC, Iain Buclaw wrote: So, I'd be willing to hear of alternatives:

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

2015-06-23 Thread Marko Anastasov via D.gnu
On Monday, 22 June 2015 at 08:56:54 UTC, Iain Buclaw wrote: So, I'd be willing to hear of alternatives: https://semaphoreci.com - However CPU's given are 2, and time to build and run tests is limited to 60 minutes. Hi Iain, Semaphore cofounder here. The first point is correct, however the