miniblog.

← Back to all posts
Feb 5, 2014 at 08:56
Using Travis CI with Jekyll is a fantastic way to find build errors. Otherwise it's easy to use a different Ruby version that doesn't error.

Related Posts

Mar 7, 2021 at 07:41
Moving all my elisp projects from Travis to GitHub actions has been a hassle, although it's getting easier with practice. I ported emacs-racer today: https://github.com/racer-rust/emacs-racer/blob/master/.github/workflows/test.yml I've learnt the hard way that it's worth testing your code both with and without byte-compilation too.
emacs-racer/.github/workflows/test.yml at master · racer-rust/emacs-racer
emacs-racer/.github/workflows/test.yml at master · racer-rust/emacs-racer
Racer support for Emacs. Contribute to racer-rust/emacs-racer development by creating an account on GitHub.
Nov 6, 2020 at 06:41
Travis CI is effectively dropping its support for open-source projects: https://www.jeffgeerling.com/blog/2020/travis-cis-new-pricing-plan-threw-wrench-my-open-source-works
Aug 15, 2020 at 23:31
I really value builds, lints and coverage metrics on pull requests. This still feels like an underexplored area though. There's no Travis equivalent AFAIK for performance. I'd love to have automatic benchmarking on contributions.