Hi,

Not sure what the perfect place to ask is, anyway...

Is there a way in travis-ci (which I see many of us use) to have one passing/failing badge per compiler? My openmethods package need at least the 2.073 front end, which gdc doesn't have yet (it seems; I never succeeded in running gdc on any of my computers). Si I'd like a pass badge for dmd and ldc2 and a fail for gdc. Possible? Go ask elsewhere?

On Sunday, 23 July 2017 at 18:34:10 UTC, Jean-Louis Leroy wrote:
> Hi,
>
> Not sure what the perfect place to ask is, anyway...
>
> Is there a way in travis-ci (which I see many of us use) to have one passing/failing badge per compiler? My openmethods package need at least the 2.073 front end, which gdc doesn't have yet (it seems; I never succeeded in running gdc on any of my computers). Si I'd like a pass badge for dmd and ldc2 and a fail for gdc. Possible? Go ask elsewhere?

Why don't you simply remove gdc from your Travis list or add it to `allow_failures` matrix?

On Sunday, 23 July 2017 at 18:34:10 UTC, Jean-Louis Leroy wrote:
> Hi,
>
> Not sure what the perfect place to ask is, anyway...
>
> Is there a way in travis-ci (which I see many of us use) to have one passing/failing badge per compiler? My openmethods package need at least the 2.073 front end, which gdc doesn't have yet (it seems; I never succeeded in running gdc on any of my computers). Si I'd like a pass badge for dmd and ldc2 and a fail for gdc. Possible? Go ask elsewhere?

That's what I've done (#1), and added a comment after the badge explaining that. However, I would really like to have per-compiler badges because 1/ my stuff needs recent compilers, and they don't all advance at the same time and 2/ as long as I cannot convince gdc to play ball with the other two, I would like to use travis-ci as a way of keeping an eye on it, in the hope it starts passing too.