This has been pointed out in the reddit thread - it's an automated platform that should make our betas much easier to work with. Thoughts?

Andrei

On Tuesday, 25 February 2014 at 01:22:57 UTC, Andrei Alexandrescu wrote:
> This has been pointed out in the reddit thread - it's an automated platform that should make our betas much easier to work with. Thoughts?
>
> Andrei

Definitely. I've been thinking about setting up something like this (even if it's a simple shared Jenkins server to begin with), but I've been travelling a lot lately, so I haven't been able to set up any hardware.

Hopefully someone will be able to get the ball rolling on this shortly. I'll keep an eye out in case I can help with anything.

On Mon, 24 Feb 2014 17:22:56 -0800, Andrei Alexandrescu <SeeWebsiteForEmail@erdani.org> wrote:

> This has been pointed out in the reddit thread - it's an automated platform that should make our betas much easier to work with. Thoughts?
>
> Andrei

I just want to point out that this will only work with Rust projects according to the info on the pages. However if you are speaking generally then this would be an absolutely fantastic addition to our build process and something that I've been asking for for a long time.

There are about a dozen tools out there that do this, but would it be worth investing more in the Auto-Tester to have it do the packaging? It already does the builds just fine. It could be taught to package and upload the latest binaries somewhere...

-- 
Adam Wilson
GitHub/IRC: LightBender
Aurora Project Coordinator

On Tuesday, 25 February 2014 at 01:22:57 UTC, Andrei Alexandrescu wrote:
> This has been pointed out in the reddit thread - it's an automated platform that should make our betas much easier to work with. Thoughts?
>
> Andrei

I don't think it is a bad idea, but as pointed out this specific project is for Rust. We could set one up for D, but that would need machines and other labor. And as Walter said, we're already pushing the build machines 24/7.

On 2/25/14, Jesse Phillips <Jesse.K.Phillips+D@gmail.com> wrote:
> I don't think it is a bad idea, but as pointed out this specific project is for Rust. We could set one up for D, but that would need machines and other labor. And as Walter said, we're already pushing the build machines 24/7.

And building binaries is easy anywho. E.g.: https://github.com/CyberShadow/Digger

On Tuesday, 25 February 2014 at 09:05:36 UTC, Andrej Mitrovic wrote:
> On 2/25/14, Jesse Phillips <Jesse.K.Phillips+D@gmail.com> wrote:
>> I don't think it is a bad idea, but as pointed out this specific
>> project is for Rust. We could set one up for D, but that would
>> need machines and other labor. And as Walter said, we're already
>> pushing the build machines 24/7.
>
> And building binaries is easy anywho. E.g.:
> https://github.com/CyberShadow/Digger

I have started a section on the wiki to list similar tools:
http://wiki.dlang.org/Building_DMD#Existing_tools

On Tuesday, 25 February 2014 at 01:42:24 UTC, Jakob Ovrum wrote:
> Definitely. I've been thinking about setting up something like this (even if it's a simple shared Jenkins server to begin with), but I've been travelling a lot lately, so I haven't been able to set up any hardware.
>
> Hopefully someone will be able to get the ball rolling on this shortly. I'll keep an eye out in case I can help with anything.

I have had plans to add automatic CI for code.dlang.org projects, got to the point where proof-of-concept was discussed with Sonke and have been distracted since than. Still can spare a single dedicated server for that.

On Tuesday, 25 February 2014 at 01:22:57 UTC, Andrei Alexandrescu wrote:
> This has been pointed out in the reddit thread - it's an automated platform that should make our betas much easier to work with. Thoughts?
>
> Andrei

I like the idea, but I think the first step would be to make sure D is officially support on Travis CI. Then start thinking about this.

--
/Jacob Carlborg

On 2/25/14, 9:48 AM, Jacob Carlborg wrote:
> On Tuesday, 25 February 2014 at 01:22:57 UTC, Andrei Alexandrescu wrote:
>> This has been pointed out in the reddit thread - it's an automated
>> platform that should make our betas much easier to work with. Thoughts?
>>
>> Andrei
>
> I like the idea, but I think the first step would be to make sure D is
> officially support on Travis CI. Then start thinking about this.
>
> --
> /Jacob Carlborg

Why do you need official support on Travis CI to do that?

On 2014-02-25 15:12, Ary Borenszweig wrote:

> Why do you need official support on Travis CI to do that?

I guess thought it would be easier to have a common way to do it.

-- 
/Jacob Carlborg