-
Notifications
You must be signed in to change notification settings - Fork 284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Travis configuration #2312
Conversation
Hum, there's a lot of duplication in the readme as to what's supported. |
84d4974
to
46b8559
Compare
1539412
to
d884dad
Compare
Well I give up on GDC for the time being... |
There is also appveyor.yml with an additional set of duplicate entries, but since updates are relatively rare, it didn't really bother me so far. |
Travis recommend removing it in a November 2018 blog post: https://blog.travis-ci.com/2018-11-19-required-linux-infrastructure-migration
Looks like the DMD 2.085.1/vibe-core failure is genuine, unfortunately, I'd suggest to simply allow it to fail for now:
(hopefully got the syntax right there) |
Looks like the DMD 2.085.1/vibe-core failure is genuine, unfortunately, I'd suggest to simply allow it to fail for now:
(hopefully got the syntax right there) |
- Drop support for 2.076 (/ LDC 1.6) - Add testing for LDC 1.15 (FE: 2.085.1) - Add testing for DMD 2.086 (LDC 1.16 is still in beta)
Trusty reached EOL 2019-04, and Travis is switching to Xenial by default: https://blog.travis-ci.com/2019-04-15-xenial-default-build-environment
It's quite outdated
Remove supported compiler before v0.8.0 Fix mention of DMD 2.062
@s-ludwig : That didn't work. Did a bit of digging and all parts of the build need to be matched, so I added |
Okay, not worth the trouble then, lets stick with 2.085.0. |
Finally green 🎉 That looked like a lot more effort than it should be, thanks for finishing this! |
This does a couple of cleanup to the travis configuration.
See the linked blog posts for the non-D-specific parts.