Jump to page: 1 2
Thread overview
Automatic documentation builds
Jun 11, 2015
Vladimir Panteleev
Jun 11, 2015
Rikki Cattermole
Jun 11, 2015
Vladimir Panteleev
Jun 11, 2015
Rikki Cattermole
Jun 11, 2015
Vladimir Panteleev
Jun 11, 2015
Rikki Cattermole
Jun 11, 2015
John Colvin
Jun 11, 2015
Vladimir Panteleev
Jun 12, 2015
Vladimir Panteleev
Jun 11, 2015
Dmitry Olshansky
Jun 11, 2015
David Gileadi
Jun 11, 2015
Vladimir Panteleev
Jun 11, 2015
Brad Roberts
Jun 11, 2015
Jonathan M Davis
Jun 11, 2015
Sönke Ludwig
Jun 11, 2015
Vladimir Panteleev
June 11, 2015
I've put together a CI system of sorts that builds the documentation for all pull requests. Hopefully this should avoid the dlang.org build breaking again in the future. It integrates with GitHub as well, and on repositories covered by Brad's auto-tester, will create a second status for the documentation. The whole thing is Digger-powered, so uses the same code as Digger and http://digger.k3.1azy.net/trend/.

Sample page: http://dtest.thecybershadow.net/results/a6e6883454a4d62c8d4b41819b9a7e33899b6222/31744d2fb90cf25ef1778f52ef640abc56c494c2/

Source code: https://github.com/CyberShadow/DAutoTest

Cool fact: When you request a built file (e.g. a .html page), it'll fetch the data directly from the Git cache repository, through a named pipe (bypassing disk) connected to a long-living Git process. This is also done transparently for included resources (images, CSS etc.)
June 11, 2015
On 12/06/2015 12:21 a.m., Vladimir Panteleev wrote:
> I've put together a CI system of sorts that builds the documentation for
> all pull requests. Hopefully this should avoid the dlang.org build
> breaking again in the future. It integrates with GitHub as well, and on
> repositories covered by Brad's auto-tester, will create a second status
> for the documentation. The whole thing is Digger-powered, so uses the
> same code as Digger and http://digger.k3.1azy.net/trend/.
>
> Sample page:
> http://dtest.thecybershadow.net/results/a6e6883454a4d62c8d4b41819b9a7e33899b6222/31744d2fb90cf25ef1778f52ef640abc56c494c2/
>
>
> Source code: https://github.com/CyberShadow/DAutoTest
>
> Cool fact: When you request a built file (e.g. a .html page), it'll
> fetch the data directly from the Git cache repository, through a named
> pipe (bypassing disk) connected to a long-living Git process. This is
> also done transparently for included resources (images, CSS etc.)

So for a PR it puts up a URL on the request?
Because this would be pretty awesome in that context!
June 11, 2015
On Thursday, 11 June 2015 at 12:27:29 UTC, Rikki Cattermole wrote:
> So for a PR it puts up a URL on the request?
> Because this would be pretty awesome in that context!

Yes, just click "Details" at the bottom of the PR page to go to the test result page.
June 11, 2015
On 12/06/2015 12:28 a.m., Vladimir Panteleev wrote:
> On Thursday, 11 June 2015 at 12:27:29 UTC, Rikki Cattermole wrote:
>> So for a PR it puts up a URL on the request?
>> Because this would be pretty awesome in that context!
>
> Yes, just click "Details" at the bottom of the PR page to go to the test
> result page.

Cool just tested it out!

Small thoughts, have some "goto" links e.g. phobos prerelease. It'll make it slightly easier to move around.
Otherwise I'm very impressed.
June 11, 2015
On 6/11/15 8:21 AM, Vladimir Panteleev wrote:
> I've put together a CI system of sorts that builds the documentation for
> all pull requests. Hopefully this should avoid the dlang.org build
> breaking again in the future. It integrates with GitHub as well, and on
> repositories covered by Brad's auto-tester, will create a second status
> for the documentation. The whole thing is Digger-powered, so uses the
> same code as Digger and http://digger.k3.1azy.net/trend/.
>
> Sample page:
> http://dtest.thecybershadow.net/results/a6e6883454a4d62c8d4b41819b9a7e33899b6222/31744d2fb90cf25ef1778f52ef640abc56c494c2/
>
>
> Source code: https://github.com/CyberShadow/DAutoTest
>
> Cool fact: When you request a built file (e.g. a .html page), it'll
> fetch the data directly from the Git cache repository, through a named
> pipe (bypassing disk) connected to a long-living Git process. This is
> also done transparently for included resources (images, CSS etc.)

This sounds really cool!

So given I have a PR, for example, https://github.com/D-Programming-Language/druntime/pull/1301

How do I find the ddoc build for it?

-Steve
June 11, 2015
On 12/06/2015 12:44 a.m., Steven Schveighoffer wrote:
> On 6/11/15 8:21 AM, Vladimir Panteleev wrote:
>> I've put together a CI system of sorts that builds the documentation for
>> all pull requests. Hopefully this should avoid the dlang.org build
>> breaking again in the future. It integrates with GitHub as well, and on
>> repositories covered by Brad's auto-tester, will create a second status
>> for the documentation. The whole thing is Digger-powered, so uses the
>> same code as Digger and http://digger.k3.1azy.net/trend/.
>>
>> Sample page:
>> http://dtest.thecybershadow.net/results/a6e6883454a4d62c8d4b41819b9a7e33899b6222/31744d2fb90cf25ef1778f52ef640abc56c494c2/
>>
>>
>>
>> Source code: https://github.com/CyberShadow/DAutoTest
>>
>> Cool fact: When you request a built file (e.g. a .html page), it'll
>> fetch the data directly from the Git cache repository, through a named
>> pipe (bypassing disk) connected to a long-living Git process. This is
>> also done transparently for included resources (images, CSS etc.)
>
> This sounds really cool!
>
> So given I have a PR, for example,
> https://github.com/D-Programming-Language/druntime/pull/1301
>
> How do I find the ddoc build for it?
>
> -Steve

Doesn't look like it has yet been added. Phobos works.
June 11, 2015
On 11-Jun-2015 15:21, Vladimir Panteleev wrote:
> I've put together a CI system of sorts that builds the documentation for
> all pull requests. Hopefully this should avoid the dlang.org build
> breaking again in the future. It integrates with GitHub as well, and on
> repositories covered by Brad's auto-tester, will create a second status
> for the documentation. The whole thing is Digger-powered, so uses the
> same code as Digger and http://digger.k3.1azy.net/trend/.
>
> Sample page:
> http://dtest.thecybershadow.net/results/a6e6883454a4d62c8d4b41819b9a7e33899b6222/31744d2fb90cf25ef1778f52ef640abc56c494c2/
>
>
> Source code: https://github.com/CyberShadow/DAutoTest
>
> Cool fact: When you request a built file (e.g. a .html page), it'll
> fetch the data directly from the Git cache repository, through a named
> pipe (bypassing disk) connected to a long-living Git process. This is
> also done transparently for included resources (images, CSS etc.)

Awesome. This is going to be a huge time saver.


-- 
Dmitry Olshansky
June 11, 2015
On 6/11/15 8:47 AM, Rikki Cattermole wrote:
>
> Doesn't look like it has yet been added. Phobos works.

Nice! I see it now. Also enabled for dlang.org.

Very cool, exactly the right UI IMO :)

-Steve
June 11, 2015
On Thursday, 11 June 2015 at 12:44:32 UTC, Steven Schveighoffer wrote:
> On 6/11/15 8:21 AM, Vladimir Panteleev wrote:
>> [...]
>
> This sounds really cool!
>
> So given I have a PR, for example, https://github.com/D-Programming-Language/druntime/pull/1301
>
> How do I find the ddoc build for it?
>
> -Steve

it doesn't seem to have triggered/finished yet for that one, but older pulls have a link in them
June 11, 2015
On 6/11/15 9:04 AM, John Colvin wrote:
> On Thursday, 11 June 2015 at 12:44:32 UTC, Steven Schveighoffer wrote:
>> On 6/11/15 8:21 AM, Vladimir Panteleev wrote:
>>> [...]
>>
>> This sounds really cool!
>>
>> So given I have a PR, for example,
>> https://github.com/D-Programming-Language/druntime/pull/1301
>>
>> How do I find the ddoc build for it?
>
> it doesn't seem to have triggered/finished yet for that one, but older
> pulls have a link in them

Yeah, hah! I seemed to have picked the only one that doesn't :)

It was the siren of seeing "DDOC:" in the title that drew me to it :P

Vladimir, this isn't a bug is it?

-Steve
« First   ‹ Prev
1 2