https://semitwist.com/travis-d-compilers

That's an auto-generated listing of all versions of DMD, GDC and LDC available on travis-ci.

It also lists the front-end (DMDFE) version used by each, and the LLVM version for each LDC (all auto-generated as well).

If the site goes down, please post an issue report at either of the project sites below. It'll ping me.

I really wanted this because I found updating the compiler lists in my .travis.yml files to be a constant pain - especially for GDC/LDC since I never have a clue which versions use which front-end or even what versions are available, and the relevant information was spread across the separate respective sites for each compiler.

Project pages for this tool (for anyone interested):
https://github.com/Abscissa/travis-dc-detect-slave
https://github.com/Abscissa/travis-dc-detect-master

Still todo:

- Auto-trigger an update check on a regular basis (I'm thinking once daily?) so I don't have to stay on top of new compiler versions and trigger an update manually. (I can use Travis's API to do this.)

- Make the listing page prettier.

On 04/26/2016 02:42 AM, Nick Sabalausky wrote:
> https://semitwist.com/travis-d-compilers
>
>...
>
> - Auto-trigger an update check on a regular basis (I'm thinking once
> daily?) so I don't have to stay on top of new compiler versions and
> trigger an update manually. (I can use Travis's API to do this.)
>

The page is now set to automatically check for updates every 24 hours. So it should always be automatically up-to-date now. No intervention needed by myself or any of the DMD/LDC/GDC developers.

On Wednesday, 27 April 2016 at 18:57:29 UTC, Nick Sabalausky wrote:
> On 04/26/2016 02:42 AM, Nick Sabalausky wrote:
>> https://semitwist.com/travis-d-compilers
>>
>>...
>>
>> - Auto-trigger an update check on a regular basis (I'm thinking once
>> daily?) so I don't have to stay on top of new compiler versions and
>> trigger an update manually. (I can use Travis's API to do this.)
>>
>
> The page is now set to automatically check for updates every 24 hours. So it should always be automatically up-to-date now. No intervention needed by myself or any of the DMD/LDC/GDC developers.

FYI you miss the available ldc alpha and betas. On purpose?

On 04/28/2016 04:03 PM, Seb wrote:
>
> FYI you miss the available ldc alpha and betas. On purpose?

Didn't initially occur to me, but I'd say that's a "possible future enhancement". It will take more work, and some extra thought, to figure out how to handle:

Right now, my tool relies on the ability to say in .travis.yml "just give me the latest available version" (by saying, ex "dmd" instead of "dmd-2.070.0"). Then my tool checks which version that turned out to be and posts it. I'm not aware of an equivalent that includes alpha/beta releases. I wonder if it would be easy enough for the folks handling D on travis to add? That would be the easiest way for me.

I *could* manually trigger it for each alpha/beta *already* available (like I did to initially populate the database with all the earlier versions of everything). I guess that would be information worth archiving. But that still doesn't give me a way to capture new alphas/betas automatically. Hmm, I do have an idea for how to do that, but it may be a little convoluted so I'd have to get to it later.

I guess...we'll see ;)

On Tuesday, 26 April 2016 at 06:42:11 UTC, Nick Sabalausky wrote:
> https://semitwist.com/travis-d-compilers
>
> I really wanted this because I found updating the compiler lists in my .travis.yml files to be a constant pain - especially for GDC/LDC since I never have a clue which versions use which front-end or even what versions are available, and the relevant information was spread across the separate respective sites for each compiler.
>

Thanks! Very useful.

On Tuesday, 26 April 2016 at 06:42:11 UTC, Nick Sabalausky wrote:
> https://semitwist.com/travis-d-compilers
>
> That's an auto-generated listing of all versions of DMD, GDC and LDC available on travis-ci.

Very useful, but perhaps you can list the string one should use to tell Travis to use that version?
What I mean is: currently the Name column says e.g. "ldc2-0.17.1", but in the travis.yml file you must specify "ldc-0.17.1" to get it (without the "2").
(If the string is incorrect, the install script will give an error message from which it is not clear at all that the compiler name is not recognized.)

Thanks,
  Johan

On 05/07/2016 05:44 AM, Johan Engelen wrote:
> What I mean is: currently the Name column says e.g. "ldc2-0.17.1", but
> in the travis.yml file you must specify "ldc-0.17.1" to get it (without
> the "2").

Ahh, you're right, I hadn't noticed that.

On Tuesday, 26 April 2016 at 06:42:11 UTC, Nick Sabalausky wrote:
> https://semitwist.com/travis-d-compilers
>
> That's an auto-generated listing of all versions of DMD, GDC and LDC available on travis-ci.
>
> [...]

Looks like semitwist.com is down. How about duplicating this list to github pages?

On 06/07/2016 12:05 PM, FreeSlave wrote:
> On Tuesday, 26 April 2016 at 06:42:11 UTC, Nick Sabalausky wrote:
>> https://semitwist.com/travis-d-compilers
>>
>> That's an auto-generated listing of all versions of DMD, GDC and LDC
>> available on travis-ci.
>>
>> [...]
>
> Looks like semitwist.com is down.

Oops. It's back up now.

> How about duplicating this list to
> github pages?

Not a bad idea.

https://github.com/Abscissa/travis-dc-detect-master/issues/4