Right now, Travis CI runs only for pull requests and pushes to branches; however, in times of inactivity1, there's a possibility for bitrot when the build doesn't run for a very long time, and it's unclear what change in the environment caused a problem.
which can automatically run a build every month on a selected branch; presumably, develop is the right choice for this project since that's where development happens, while the master branch is the latest stable release. To improve efficiency, you can enable the option to only run a cron job build if there hasn't been a build already run recently on that branch (see the drop-down next to "Options").
Right now, Travis CI runs only for pull requests and pushes to branches; however, in times of inactivity1, there's a possibility for bitrot when the build doesn't run for a very long time, and it's unclear what change in the environment caused a problem.
Travis CI has a feature called cron jobs:
which can automatically run a build every month on a selected branch; presumably,
developis the right choice for this project since that's where development happens, while themasterbranch is the latest stable release. To improve efficiency, you can enable the option to only run a cron job build if there hasn't been a build already run recently on that branch (see the drop-down next to "Options").Thanks!
1 Such as the most recent case, where there haven't been commits for a year; see PR https://github.com/metal/metal.js/pull/413, issue https://github.com/metal/metal.js/issues/414, and issue https://github.com/metal/metal.js/issues/415 for context.