Hello all,

GitHub very nicely ensures that all pull requests to dmd, druntime and phobos are sent to the auto-tester and that success/failure reports are sent back.

But ... how is this done?  Is the auto-tester entirely custom written or does it use some standard tools?  And how is it hooked into GitHub?

Thanks & best wishes,

    -- Joe

On 2013-09-24 12:25, Joseph Rushton Wakeling wrote:
> Hello all,
>
> GitHub very nicely ensures that all pull requests to dmd, druntime and
> phobos are sent to the auto-tester and that success/failure reports are
> sent back.
>
> But ... how is this done?  Is the auto-tester entirely custom written or
> does it use some standard tools?  And how is it hooked into GitHub?

It's custom. I would guess it either uses a git hook or it uses some API provided by Github.

-- 
/Jacob Carlborg

On Tuesday, 24 September 2013 at 10:25:21 UTC, Joseph Rushton Wakeling wrote:
> Hello all,
>
> GitHub very nicely ensures that all pull requests to dmd, druntime and phobos are sent to the auto-tester and that success/failure reports are sent back.
>
> But ... how is this done?  Is the auto-tester entirely custom written or does it use some standard tools?  And how is it hooked into GitHub?
>
> Thanks & best wishes,
>
>     -- Joe

D one is custom but most major CI tools have such functionality (I personally have used Jenkins). It uses GitHub application API and needs to be explicitly allowed by repository owner.

On 24/09/13 13:01, Jacob Carlborg wrote:
> It's custom. I would guess it either uses a git hook or it uses some API
> provided by Github.

Ahh, OK.  I was wondering if it used some standard tool to manage starting the test jobs and reporting back the tests -- something like Gerrit, Jenkins, etc. I don't have any personal experience of these so couldn't tell on the basis of the test website.

Thanks for the info! :-)

On 9/24/13 4:29 AM, Joseph Rushton Wakeling wrote:
> On 24/09/13 13:01, Jacob Carlborg wrote:
>> It's custom. I would guess it either uses a git hook or it uses some API
>> provided by Github.
>
> Ahh, OK.  I was wondering if it used some standard tool to manage starting the test jobs and
> reporting back the tests -- something like Gerrit, Jenkins, etc. I don't have any personal
> experience of these so couldn't tell on the basis of the test website.
>
> Thanks for the info! :-)

https://github.com/braddr/d-tester

I'd use a standard tool (or would have, silly to switch when this one does the job) but none of them support the combination of features used.  Primarily: github, testing on multiple platforms, testing pulls as merges into the target branch (rather than just the pull itself), multiple repositories in the same build.  There's probably more requirements, it's been a while since I researched the state of the ecosystem and exactly what the gaps are.

But now that it's written, it's just fundamentally not that much code, nor is it actually difficult code.

On 2013-09-24 18:25, Brad Roberts wrote:

> https://github.com/braddr/d-tester

Could you add a link to this on the test results page? I always forget where this code is located.

-- 
/Jacob Carlborg

On Wednesday, 25 September 2013 at 06:51:44 UTC, Jacob Carlborg wrote:
> On 2013-09-24 18:25, Brad Roberts wrote:
>
>> https://github.com/braddr/d-tester
>
> Could you add a link to this on the test results page? I always forget where this code is located.

http://d.puremagic.com/test-results/

On 2013-09-25 09:30, simendsjo wrote:

> http://d.puremagic.com/test-results/

I know where the test results are. But, what I'm forgetting is where the code is which implements these test results. I want this page:

http://d.puremagic.com/test-results/

To have a link to this:

https://github.com/braddr/d-tester

-- 
/Jacob Carlborg

On Wednesday, 25 September 2013 at 11:29:16 UTC, Jacob Carlborg wrote:
> On 2013-09-25 09:30, simendsjo wrote:
>
>> http://d.puremagic.com/test-results/
>
> I know where the test results are. But, what I'm forgetting is where the code is which implements these test results. I want this page:
>
> http://d.puremagic.com/test-results/
>
> To have a link to this:
>
> https://github.com/braddr/d-tester

Seems like I didn't actually read you post :)

On 24/09/13 18:25, Brad Roberts wrote:
> I'd use a standard tool (or would have, silly to switch when this one does the
> job) but none of them support the combination of features used.  Primarily:
> github, testing on multiple platforms, testing pulls as merges into the target
> branch (rather than just the pull itself), multiple repositories in the same
> build.  There's probably more requirements, it's been a while since I researched
> the state of the ecosystem and exactly what the gaps are.
>
> But now that it's written, it's just fundamentally not that much code, nor is it
> actually difficult code.

Thanks very much for pointing me to that.  I'm looking into auto-testing stuff that would work with a project hosted on Gitorious (GitHub is unsatisfactory for political reasons) -- I'm working on the assumption that one of the standard testing frameworks will play nice with that (I've seen a writeup on Gerrit + Gitorious), but assuming anything custom is required, this could be a very useful template.