On 2018-03-03 07:39, Nick Sabalausky (Abscissa) wrote:
Certainly a possible approach, but has downsides:
- Maybe there's a simple setting I've overlooked, but when a build job
fails on travis, the author does not get proactively notified. The
author only finds out next time they go into travis. (I've been
surprised many times to discover failed builds that had occured several
days ago, or more.)
You should get an email notification about failed builds [1] [2],
- A project author will still need to: 1. Actively notice new compiler
releases and 2. Manually update the .travis.yml files for each of their
projects. Certainly there's room for more automation here.
No. If you specify "dmd" (without any version) in the list of compilers
[5], it will build the latest version. For example, this build [3],
which ran 23 hours ago uses DMD 2.078.3, while this one [4], 29 days
ago, uses 2.078.2. As you can see on the commit in Travis CI, it's the
same commit.
- Except when "nightly" is desired, this leads to many unnecessary
redundant builds/tests, especially across all the various D projects.
(Though I don't know how much that would matter on travis. Maybe it'd be
a drop in their bucket.)
[1]
https://docs.travis-ci.com/user/notifications/#Default-notification-settings
[2]
https://docs.travis-ci.com/user/notifications/#Missing-build-notifications
[3] https://travis-ci.org/jacob-carlborg/dstep/jobs/348275710
[4] https://travis-ci.org/jacob-carlborg/dstep/jobs/340527251
[5] https://github.com/jacob-carlborg/dstep/blob/master/.travis.yml#L4
--
/Jacob Carlborg
